From: Eric Mangold <teratorn@world-net.net>
To: Dominic Mitchell <dom@happygiraffe.net>
Cc: "zsh-users@sunsite.dk" <zsh-users@sunsite.dk>
Subject: Re: Adding new completions to zsh
Date: Thu, 26 Feb 2004 14:56:59 -0700 [thread overview]
Message-ID: <opr3zy89mci4eeqj@mail.oaktech.net> (raw)
In-Reply-To: <20040226213704.GA91706@ppe.happygiraffe.net>
On Thu, 26 Feb 2004 21:37:04 +0000, Dominic Mitchell
<dom@happygiraffe.net> wrote:
> On Wed, Feb 25, 2004 at 08:39:22PM -0700, Eric Mangold wrote:
>> My idea for allowing greater flexibility is to bundle the actual zsh
>> completion functionality as part of the Twisted distribution and give
>> zsh
>> a "stub" that will use the completion functions that are bundled with
>> Twisted.
>
> Would it not make more sense to get your extensions bundled with Twisted
> and then installed in the site-functions directory? This is what the
> FreeBSD portupgrade commands do and it works great!
I've considered this, however I don't believe it is ideal for this
specific situation. There are a couple different scenarios where using the
completion info installed by Twisted's installion routine would be
undesireable.
First, there's no guarantee that the user even has Twisted /installed/. It
is very common for the users and developers of Twisted to be working
directly out of a CVS checkout. They will do this by adding the directory
containing the CVS checkout to their PYTHONPATH env var.
Secondly, the user may have a release version of Twisted installed yet be
using another version somewhere else. Such as CVS or having simply
extracted a newer Twisted release tarball in their home dir and set
PYTHONPATH accordingly.
So asking python is the only sure way to provide info that is accurate for
what the user is presently doing.
-Eric
prev parent reply other threads:[~2004-02-26 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 3:39 Eric Mangold
2004-02-26 10:29 ` Peter Stephenson
2004-02-26 21:42 ` Eric Mangold
2004-02-26 11:12 ` Oliver Kiddle
2004-02-26 21:37 ` Dominic Mitchell
2004-02-26 21:56 ` Eric Mangold [this message]
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=opr3zy89mci4eeqj@mail.oaktech.net \
--to=teratorn@world-net.net \
--cc=dom@happygiraffe.net \
--cc=zsh-users@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).