From: Bruce Stephens <B.Stephens@isode.com>
To: zsh-workers@math.gatech.edu
Subject: Re: comments in completion
Date: Mon, 17 Nov 1997 13:54:36 +0000 [thread overview]
Message-ID: <199711171354.IAA01254@math.gatech.edu> (raw)
In-Reply-To: Your message of "Sun, 16 Nov 1997 09:26:26 PST." <971116092626.ZM19655@candle.brasslantern.com>
schaefer@brasslantern.com said:
> The problem with job numbers and process IDs is that you have to
> generate the explanation on the fly. Maybe what we need is a way to
> run a function to provide the -X output, rather than having only a
> fixed string.
Yes, we definitely want this. I've wanted for a while to get used to using
the directory stack thingy (apart from just popd and the autopushd option),
and having nice completion would be really useful for this.
A better way to do it might be to extend the programmable completion a bit, so
the function could set both the list of possibilities and a list of
descriptions of them. That sounds a bit less hairy than yet another compctl
flag, although I can see arguments both ways.
next prev parent reply other threads:[~1997-11-17 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-16 15:44 Stefan Monnier
1997-11-16 17:26 ` Bart Schaefer
1997-11-17 13:54 ` Bruce Stephens [this message]
1997-11-17 15:45 ` Bart Schaefer
1997-11-17 16:26 ` Bruce Stephens
1997-11-17 17:13 ` Bart Schaefer
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=199711171354.IAA01254@math.gatech.edu \
--to=b.stephens@isode.com \
--cc=zsh-workers@math.gatech.edu \
/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).