From: Oliver Kiddle <opk@u.genie.co.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: completion for file descriptors
Date: Thu, 20 Apr 2000 10:19:26 +0100 [thread overview]
Message-ID: <38FECB9E.39061965@u.genie.co.uk> (raw)
In-Reply-To: <200004200718.JAA24905@beta.informatik.hu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]
Sven Wischnowsky wrote:
> Yes, function moving and ordering before 4.0...
What you suggest for the basic stuff sounds good to me.
> The other stuff is harder to decide. _rpm, for example can also be
> useful on non-Linux systems. I don't know debian, but I guess the
> commands from that directory can be useful elsewhere, too. So maybe we
> should package the functions in a way that reflects what the commands
> do (network, package-managers, ...).
That is a bit more diffcult. I think I would prefer to stick to
directories which group together commands which users will generally
have all or none of as it is easier to specify whether you want a whole
directory than to pick and choose from specific commands taking each on
their own. I expect that it is fairly rare for someone to use rpm on
something other than Linux. Would there be problems involved in making
the installation of the functions intelligently only pick out
completions for commands which exist on the system?
> (And now Andrej comes and
> says that we should put all the GNU commands on the side... which
> wouldn't work with the ordering-by-what-they-do, of course. I still
> think there should be only one function per command and we try to find
> out what to complete by investigating the environment inside the
> functions.)
I agree with you on this. It keeps things all together better than if we
say had 10 different completions for the same command on different
systems so it is easier to make useful changes affect all the different
systems where they have commonality. It is common for GNU stuff to be
installed alongside originals, sometimes in a different directory and
sometimes with a different name and it would be important to me that
completion for these works.
I've attached my AIX specific completions. I haven't put them in cvs or
anything but when you (or whoever) come to sort out the directories, a
place could be found for them (and those FreeBSD ones someone sent
yesterday). I've actually got a few more AIX (and IRIX) completions but
they are very old (pre-_arguments) and could really do with a rewrite.
Oliver
[-- Attachment #2: Aixcomps.tgz --]
[-- Type: application/x-unknown-content-type-WinZip, Size: 1662 bytes --]
next prev parent reply other threads:[~2000-04-20 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-20 7:18 Sven Wischnowsky
2000-04-20 9:19 ` Oliver Kiddle [this message]
2000-04-20 9:31 ` Thomas Köhler
2000-04-24 5:23 ` Completion function directories Bart Schaefer
2000-04-27 7:59 ` Andrej Borsenkow
2000-04-27 22:09 ` Bart Schaefer
2000-05-01 2:43 ` PATCH: Spelling corrections in Etc/ files Oliver Kiddle
-- strict thread matches above, loose matches on Subject: below --
2000-04-20 11:10 PATCH: completion for file descriptors Sven Wischnowsky
2000-04-20 9:54 Sven Wischnowsky
2000-04-20 10:58 ` Oliver Kiddle
2000-04-19 23:41 Oliver Kiddle
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=38FECB9E.39061965@u.genie.co.uk \
--to=opk@u.genie.co.uk \
--cc=zsh-workers@sunsite.auc.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).