From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: improvement to user@host completions
Date: Mon, 11 Oct 1999 13:22:19 +0200 (MET DST) [thread overview]
Message-ID: <199910111122.NAA03139@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Adam Spiers's message of Mon, 27 Sep 1999 00:28:09 +0100
Adam Spiers wrote:
> There's also the `Completion System Configuration' section of the info
> pages. Is it a deliberate choice that descriptions of most of the
> standard completion functions (e.g. _dirs, _users, _groups) are
> missing from the info pages? If not, should they go in the `Utility
> Functions' section, or maybe in a new section immediately following it?
Deliberate in the sense that noone (at least not me) took the time to
write that. *But* I already wished we had it, too. So, if you offer to
write them: yes, please ;-)
I'd vote for a separate section because the function in `Utility
Functions' don't generate the matches themselves, they are told what
should be added, whereas functions like `_users' decide that for
themselves.
(This may also be a bit of a banana problem: `_x_colors' and friends?)
> Out of curiosity, has anyone any ideas on what the official release
> plans are for the near future? 3.1.7 soon, or not? Are there any
> more big plans for 3.2?
At least I am only still dreaming of a generic package system (to
replace the ad hoc compinit and friends) and of a cleanup for the
keymap stuff.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-10-11 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-11 11:22 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-26 14:17 Adam Spiers
1999-09-26 15:02 ` Peter Stephenson
1999-09-26 16:57 ` Bart Schaefer
1999-09-26 23:28 ` Adam Spiers
1999-09-27 7:54 ` Tanaka Akira
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=199910111122.NAA03139@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).