From: Aron Griffis <agriffis@gentoo.org>
To: list gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Re: new local USE var: vim-with-x
Date: Tue, 29 Apr 2003 09:10:37 -0400 [thread overview]
Message-ID: <20030429131036.GC413@time> (raw)
In-Reply-To: <1051598177.1819.32.camel@bunyip.uwa.edu.au>
Bill Kenworthy wrote: [Tue Apr 29 2003, 02:36:17AM EDT]
> Because if you build vim with X in your use flags and you try and run
> "vim" from a non-X console or a console ssh session it wont run! I
> have had to stuff around compiling vim with USE="-X" with two machines
> now so I could fix other problems from a console remote login. vim
> should default to -X unless overidden specifically and locally. Note
> that you do want X support for most other apps though, so honouring a
> global USE is not a good idea for vim..
Just to throw one more thought out there... The behavior you describe
above is actually a bug. It's fixed in vim 6.1.474 and in 6.2a. I
haven't put 6.1.474 into portage because of the existence of 6.2a and
because I don't know if there's a gtk2 patch for 6.1.474.
The bug is this: vim normally detects if the X connection fails and
falls back to pure text mode. However for a while during the 6.1
patches, it would fail under some circumstances and return you to a
prompt.
In truth the fact that this bug has been remedied makes it more
plausible to depend on the global USE=X, but I'm still concerned about
first-time installs.
Aron
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-29 13:10 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 0:14 [gentoo-dev] new local USE var: vim-with-x Aron Griffis
2003-04-29 1:16 ` [gentoo-dev] " Björn Lindström
2003-04-29 3:32 ` Aron Griffis
2003-04-29 6:24 ` Mike Lundy
2003-04-29 6:36 ` Bill Kenworthy
2003-04-29 10:07 ` Patrick Börjesson
2003-04-29 10:23 ` Chris Watson
2003-04-29 11:52 ` Patrick Kursawe
2003-04-29 10:08 ` Mark Gordon
2003-04-29 13:05 ` Björn Lindström
2003-04-29 13:12 ` Fredrik Jagenheim
2003-04-29 13:18 ` Björn Lindström
2003-04-29 13:27 ` Bartosch Pixa
2003-04-29 13:38 ` Fredrik Jagenheim
2003-04-29 13:44 ` William Kenworthy
2003-04-29 15:27 ` Björn Lindström
2003-04-29 13:10 ` Aron Griffis [this message]
2003-04-29 14:13 ` Mark Gordon
2003-04-29 15:00 ` [gentoo-dev] Was: (Re: new local USE var: vim-with-x ) Default USE Flags Revision Adrian Almenar
2003-04-29 15:05 ` Jon Portnoy
2003-04-29 15:09 ` Daniel Armyr
2003-04-29 13:56 ` [gentoo-dev] Re: new local USE var: vim-with-x Max Kalika
2003-04-29 14:22 ` Daniel Armyr
2003-04-29 14:49 ` Max Kalika
2003-04-29 15:31 ` Caleb Shay
2003-04-29 16:05 ` William Kenworthy
2003-04-29 18:28 ` Björn Lindström
2003-04-29 19:41 ` Mark Gordon
2003-04-29 23:49 ` William Kenworthy
2003-04-30 0:29 ` Peter Fein
2003-04-30 0:47 ` William Kenworthy
2003-04-30 23:31 ` Björn Lindström
2003-04-30 12:41 ` James H. Cloos Jr.
2003-04-29 18:46 ` torbenh
2003-04-29 18:55 ` Dan Armak
2003-05-01 14:16 ` Brad Laue
2003-04-30 13:26 ` Celestial Wizard
2003-04-29 13:01 ` Björn Lindström
2003-04-29 18:16 ` Martin Schlemmer
2003-04-29 20:10 ` Aron Griffis
2003-04-29 15:46 ` [gentoo-dev] " Grant Goodyear
2003-05-01 3:25 ` Troy Dack
2003-04-30 14:08 ` William Kenworthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030429131036.GC413@time \
--to=agriffis@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox