[gentoo-dev] VIMRUNTIME

[gentoo-dev] VIMRUNTIME

[Aron Griffis]

(please respond on -dev, not -core)

Hi folks,

This is just a heads-up regarding the vim ebuilds and eclass.  Yesterday
I added 6.2a (aka 6.2_pre1) to the tree.  It's ~ masked but works fine.
Hopefully I'll be able to unmask it during the next package upgrades
phase.

Here are a couple notes:

1. I've removed the setting of VIMRUNTIME from the ebuild.  This was
   installing /etc/env.d/40vim.  There is no reason to set this
   variable, since the vim binary has compiled in the location of the
   run-time files, /usr/share/vim/vim62a.  I have verified this works
   for every vim ebuild in the tree, so I don't know what motivated the
   "fix" in the first place.

   However when you update to the new version, you'll probably notice
   that running "vim" (or any of the variants) gives you some warnings,
   along with syntax highlighting not working, etc.  This is because you
   still have VIMRUNTIME in your environment.  It won't disappear until
   you logout and back in.  I'm sorry, but there's no real way to climb
   up the process tree and remove VIMRUNTIME from the environment of
   each process... :-/

2. Part of my experimentation revealed that vim doesn't yet work with
   ruby-1.8.x.  I'll be working on this eventually to find and fix the
   problem, but for the moment I simply did

        DEPEND="ruby? ( =ruby-1.6* )"

   You might wonder, why not 1.6.*?  Well, Portage didn't like that.
   Something to figure out another time.

3. 6.2a says "6.2 alpha".  It's hardly alpha.  It's really just 6.1 plus
   all 474 patches plus gtk2 support.  That's why I would consider
   marking this stable.

4. This version introduces motif support, so now gvim can produce
   an athena, gtk, gtk2, gnome, or motif binary depending on your USE
   flags.

Have fun and let me know of bugs via bugzilla.  I'll be away until
Monday so I won't be responding to email until then.

Aron

--
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Re: [gentoo-core] VIMRUNTIME

[Martin Schlemmer]

[-- Attachment #1: Type: text/plain, Size: 690 bytes --]

On Fri, 2003-04-25 at 06:41, Aron Griffis wrote:

> 1. I've removed the setting of VIMRUNTIME from the ebuild.  This was
>    installing /etc/env.d/40vim.  There is no reason to set this
>    variable, since the vim binary has compiled in the location of the
>    run-time files, /usr/share/vim/vim62a.  I have verified this works
>    for every vim ebuild in the tree, so I don't know what motivated the
>    "fix" in the first place.
> 

I added it, as around 6.0/6.1, it did not even wanted to find its own
help files :/  If it works now again though, fine.



-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa




[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] VIMRUNTIME

[Aron Griffis]

Aron Griffis wrote:[Fri Apr 25 2003, 12:41:32AM EDT]
>    However when you update to the new version, you'll probably notice
>    that running "vim" (or any of the variants) gives you some warnings,
>    along with syntax highlighting not working, etc.  This is because you
>    still have VIMRUNTIME in your environment.  It won't disappear until
>    you logout and back in.  I'm sorry, but there's no real way to climb
>    up the process tree and remove VIMRUNTIME from the environment of
>    each process... :-/

Of course you can "unset VIMRUNTIME" in any given shell.

> 4. This version introduces motif support, so now gvim can produce
>    an athena, gtk, gtk2, gnome, or motif binary depending on your USE
>    flags.

These are prioritized, so here are the combinations you would need:

  gtk2: USE="gtk2" emerge gvim
 gnome: USE="-gtk2 gnome" emerge gvim
   gtk: USE="-gtk2 -gnome gtk" emerge gvim
 motif: USE="-gtk2 -gnome -gtk motif" emerge gvim
athena: USE="-gtk2 -gnome -gtk -motif X" emerge gvim

Aron

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] VIMRUNTIME

[Thomas Weidner]

Aron Griffis wrote:

>3. 6.2a says "6.2 alpha".  It's hardly alpha.  It's really just 6.1 plus
>   all 474 patches plus gtk2 support.  That's why I would consider
>   marking this stable.
>
from the vim 6.2a announcement:
``Note that test 49 fails (it tests the ":try" command). It even crashes
Vim sometimes. Hopefully this can be fixed soon. I didn't spot an
obvious problem.''
sounds not very stable to me.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] VIMRUNTIME

[Aron Griffis]

[-- Attachment #1: Type: text/plain, Size: 718 bytes --]

Thomas Weidner wrote:[Fri Apr 25 2003, 10:21:47AM EDT]
> from the vim 6.2a announcement:
> ``Note that test 49 fails (it tests the ":try" command). It even crashes
> Vim sometimes. Hopefully this can be fixed soon. I didn't spot an
> obvious problem.''
> sounds not very stable to me.

Since this is new functionality added to 6.2a (try/catch), I'm not too
concerned about it.  All your current 6.1 functionality should be more
stable with this version than any prior due to the inclusion of all the
6.1 patches.

The other option would be to provide another 6.1 ebuild that would
include all the patches but exclude (of course) the try/catch
functionality included in 6.2a.  This doesn't seem worthwhile to me.

Aron

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] VIMRUNTIME

[Lars Weiler]

Just an annotation for the use of GUI dialogs in gvim.

I'm using the xmledit ftplugin script for editing XML-files.
It has support for GUI dialogs in gvim, e.g. when you wrap a
new element around a visual selection (mark selection, then
type \x ).

In (g)vim 6.2c it crashed without any reason, when you run
into a situation where you need GUI dialogs.  After a
reemerge of gvim with USE="vim-with-x" it functions proper
again.  Should not "vim-with-x" be default for gvim?

Regards, Lars

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] VIMRUNTIME

[Luke-Jr]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The reason why X is disabled by default with vim is because, IIRC, the 
maintainer doesn't want people to have to emerge X before emerging vim (don't 
know what's wrong with "USE=-X emerge vim").
As mentioned in another thread, Portage doesn't have any way to depend on "pkg 
compiled with this USE flag", only "package".
Depending on how vim-core is being implemented, it may or may not be possible 
to resolve this problem without support from Portage.
Has it been reported in Bugzilla?

On Tuesday 13 May 2003 12:03 am, Lars Weiler wrote:
> Just an annotation for the use of GUI dialogs in gvim.
>
> I'm using the xmledit ftplugin script for editing XML-files.
> It has support for GUI dialogs in gvim, e.g. when you wrap a
> new element around a visual selection (mark selection, then
> type \x ).
>
> In (g)vim 6.2c it crashed without any reason, when you run
> into a situation where you need GUI dialogs.  After a
> reemerge of gvim with USE="vim-with-x" it functions proper
> again.  Should not "vim-with-x" be default for gvim?
>
> Regards, Lars
>
> --
> gentoo-dev@gentoo.org mailing list
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+wEH1Zl/BHdU+lYMRAngdAKCH3dbB6iuYY8xXNwiG8LUke28+QACeIWMf
/RfMeRhOPjugEfkH3m2S5Zo=
=lwF7
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list