| 1 |
Strange - plenty! vim is a console program and gvim and kvim are X |
| 2 |
based - so until I had a failure and needed a pure console vim, I didnt |
| 3 |
know this would occur. True you can compile vim with X hooks, but why |
| 4 |
in a console based program?, when it means that on a system that has |
| 5 |
failed i.e., see how many (including me!) people have had X failures |
| 6 |
when installing xfree-4.3. vim is my fallback editor for when gvim isnt |
| 7 |
available, and all of a sudden, it fails right when I need it most! |
| 8 |
|
| 9 |
Perhaps we need a 4th package to keep the frustrated X types happy - |
| 10 |
vim-with-x, rather than a USE variable which is just not up to this |
| 11 |
task. Then everyone can install the vim that suits them, e.g., vim, |
| 12 |
xvim, kvim and gvim. |
| 13 |
|
| 14 |
BillK |
| 15 |
|
| 16 |
|
| 17 |
On Tue, 2003-04-29 at 21:05, Björn Lindström wrote: |
| 18 |
> Bill Kenworthy <billk@×××××××××.au> [20030429 08:36]: |
| 19 |
> > Because if you build vim with X in your use flags and you try and run |
| 20 |
> > "vim" from a non-X console or a console ssh session it wont run! I |
| 21 |
> > have had to stuff around compiling vim with USE="-X" with two machines |
| 22 |
> > now so I could fix other problems from a console remote login. |
| 23 |
> |
| 24 |
> That's easy to fix. Just let "emerge vim" with USE=X install |
| 25 |
> /usr/bin/vim as a text mode vim _and_ /usr/bin/(g|k)vim as the GUI |
| 26 |
> version. |
| 27 |
> |
| 28 |
> > vim should default to -X unless overidden specifically and locally. |
| 29 |
> > Note that you do want X support for most other apps though, so |
| 30 |
> > honouring a global USE is not a good idea for vim.. |
| 31 |
> |
| 32 |
> I still think this is ugly. If you asked for X support, you get it. |
| 33 |
> What's so strange about that? |
| 34 |
-- |
| 35 |
William Kenworthy <billk@×××××××××.au> |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives