1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
The reason why X is disabled by default with vim is because, IIRC, the |
5 |
maintainer doesn't want people to have to emerge X before emerging vim (don't |
6 |
know what's wrong with "USE=-X emerge vim"). |
7 |
As mentioned in another thread, Portage doesn't have any way to depend on "pkg |
8 |
compiled with this USE flag", only "package". |
9 |
Depending on how vim-core is being implemented, it may or may not be possible |
10 |
to resolve this problem without support from Portage. |
11 |
Has it been reported in Bugzilla? |
12 |
|
13 |
On Tuesday 13 May 2003 12:03 am, Lars Weiler wrote: |
14 |
> Just an annotation for the use of GUI dialogs in gvim. |
15 |
> |
16 |
> I'm using the xmledit ftplugin script for editing XML-files. |
17 |
> It has support for GUI dialogs in gvim, e.g. when you wrap a |
18 |
> new element around a visual selection (mark selection, then |
19 |
> type \x ). |
20 |
> |
21 |
> In (g)vim 6.2c it crashed without any reason, when you run |
22 |
> into a situation where you need GUI dialogs. After a |
23 |
> reemerge of gvim with USE="vim-with-x" it functions proper |
24 |
> again. Should not "vim-with-x" be default for gvim? |
25 |
> |
26 |
> Regards, Lars |
27 |
> |
28 |
> -- |
29 |
> gentoo-dev@g.o mailing list |
30 |
-----BEGIN PGP SIGNATURE----- |
31 |
Version: GnuPG v1.2.2 (GNU/Linux) |
32 |
|
33 |
iD8DBQE+wEH1Zl/BHdU+lYMRAngdAKCH3dbB6iuYY8xXNwiG8LUke28+QACeIWMf |
34 |
/RfMeRhOPjugEfkH3m2S5Zo= |
35 |
=lwF7 |
36 |
-----END PGP SIGNATURE----- |
37 |
|
38 |
|
39 |
-- |
40 |
gentoo-dev@g.o mailing list |