From: Jim Ramsay <lack@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] app-editors/vim and USE="vim-with-x" -> Rename to USE="X"?
Date: Mon, 7 Jun 2010 15:59:13 -0400 [thread overview]
Message-ID: <20100607155913.23600005@vrm378-02.vrm378.am.mot.com> (raw)
In-Reply-To: <20100607201031.5a8cc1b6@snowcone>
[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]
Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
> On Mon, 7 Jun 2010 23:05:27 +0400
> dev-random@mail.ru wrote:
> > On Mon, Jun 07, 2010 at 07:53:22PM +0100, Ciaran McCreesh wrote:
> > > It's there because if you break your X you probably want a usable
> > > editor to help you fix it.
> >
> > vim, compiled with "vim-with-x" works correctly when X is broken. It
> > doesn't enable X11-based UI, like flag "X" suggests. It just enables
> > optional connection to x-server to use its clipboard, and vim still
> > works if that connection fails.
>
> It does not, however, work if your X libraries are broken.
I certainly agree with you that removing the linkage to a handful of X
libraries makes vim more robust if those particular libraries fail.
However even with USE="-vim-with-x", there are a number of other
libraries that, if broken, will still render vim useless, such as
ncurses, perl, python, and ruby.
I suspect if one really wants a fail-proof editor, one would either
be building vim with USE="minimal" which will ignore the 'vim-with-x'
or 'X' USE flag (regardless of what we call it) and also ignore any
perl/python/ruby libraries, or one would want something more
trim, like busybox vi. Or even better yet, busybox vi with USE="static".
Of course changing the USE flag name to 'X' would still let users
decide to *not* link their app-editors/vim against any X libraries via
per-package USE flags. The main difference in changing the name from
'vim-with-x' to 'X' is that instead of enforcing a default behaviour of
"Vim will not link against X unless explicitly told to do so", we will
be enforcing a policy of "Vim will link against X when USE='X'".
I suppose this is a bit like a transition from an opt-in policy to an
opt-out policy, with the caveat that by enabling USE=X globally, a user
has already declared their intent: opt-in to linking against X
in all packages where there is a choice to do so.
--
Jim Ramsay
Gentoo Developer (rox/fluxbox/gkrellm/vim)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-07 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 18:44 [gentoo-dev] app-editors/vim and USE="vim-with-x" -> Rename to USE="X"? Jim Ramsay
2010-06-07 18:51 ` Tomáš Chvátal
2010-06-07 18:53 ` Ciaran McCreesh
2010-06-07 19:05 ` dev-random
2010-06-07 19:10 ` Ciaran McCreesh
2010-06-07 19:59 ` Jim Ramsay [this message]
2010-06-07 20:38 ` [gentoo-dev] " Duncan
2010-06-08 17:29 ` [gentoo-dev] " Michał Górny
2010-06-08 20:30 ` Mike Frysinger
2010-06-09 21:27 ` Jim Ramsay
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=20100607155913.23600005@vrm378-02.vrm378.am.mot.com \
--to=lack@gentoo.org \
--cc=gentoo-dev@lists.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