From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11112 invoked by uid 1002); 30 Apr 2003 00:29:16 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 28726 invoked from network); 30 Apr 2003 00:29:16 -0000 Date: Tue, 29 Apr 2003 19:29:14 -0500 From: Peter Fein To: billk@iinet.net.au Cc: gentoo-dev List Message-Id: <20030429192914.3a70ea62.pfein@pobox.com> In-Reply-To: <1051660150.24674.1610.camel@rattus.Localdomain> References: <20030429001443.GA413@time> <20030429011644.GB18711@lucien.dreaming> <20030429033239.GB413@time> <200304290224.53881.novas007@gmx.net> <1051598177.1819.32.camel@bunyip.uwa.edu.au> <1620000.1051624615@[192.168.23.6]> <3EAE8AC3.8060603@home.se> <1250000.1051627788@[192.168.23.6]> <1051630278.19658.24.camel@chinstrap.penguins.homeunix.net> <1051632346.24684.213.camel@rattus.Localdomain> <20030429182847.GH18711@lucien.dreaming> <1051660150.24674.1610.camel@rattus.Localdomain> X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] Re: new local USE var: vim-with-x X-Archives-Salt: 84b7fc54-2367-4ce7-9378-fcf7474fb9f9 X-Archives-Hash: c3c79bfcbb906ba8f4b08488c731580b On 30 Apr 2003 07:49:10 +0800 William Kenworthy wrote: > This was apparently a bug in vim at one time, but even the bugfixed > console version can want X in some circumstances that are likely to > catch people out when can they least expect or afford it (e.g., X > failure: how do you edit XF86Config quickly if you have no X and > therefore no vim: has happened to me!). This is just a silly reason already - did you nuke nano or something? >>From vim --help: -X Do not connect to X server Users who can't figure out to try --help are probably going to generate line noise by trying to use vi in the first place. ;) > To me, the question is whether to stick with a convention that is not > appropriate in this circumstance, or do a logical workaround that can > satisfactorily overcome this behaviour. While we can continue the vim-with-x vs. X battle royale, I: a) think X is better b) really don't care c) withdraw any ill-will toward developers who avoid -dev d) was seriously hoping this would turn in to a vi vs. emacs war Perhaps someone should set up a forum poll? ;) > Can someone define why console vim needs X anyway, apart from the highly > critical trick of putting a title on the X window? Causing grief to those who bork their XF86Config? ;) (All flames meant in the friendliest spirit.) -- Peter Fein pfein@pobox.com 773-575-0694 -- gentoo-dev@gentoo.org mailing list