From: Cesar Crusius <crusius@barcelonadesign.com>
To: zsh-users@sunsite.dk
Subject: Re: compctl -y problem.
Date: Tue, 29 May 2001 08:41:16 -0700 [thread overview]
Message-ID: <E154lcS-0004Z0-00@sevilla> (raw)
In reply to "Bart Schaefer" <schaefer@candle.brasslantern.com>
>
>(Part of this thread went to zsh-workers ... returning now to zsh-users
>with a workaround)
>
>On May 25, 3:11pm, Bart Schaefer wrote:
>}
>} I know Sven won't be thrilled about being asked to fix anything in the
>} old compctl code ... perhaps we should just remove the `-y' option, as
>} it's new since 3.0 anyway, and document the correct way to achieve the
>} same effect by using the new completion system (which, incidentally, I
>} don't know how to do ... `compadd -d' doesn't quite cut it).
>
>I don't know what the output of `aereport changes` looks like, so it may
>be that there's a simpler solution. For example, if the same number of
>lines will be returned by `aereport changes -unf` and `... -terse`, this
>will work:
>
>function _aecd {
> local change_descriptions reply
> change_descriptions=(${(f)"$(aereport changes -unf | grep -v completed)"})
> reply=($(aereport changes -terse | grep -v completed | sed -e 's/ .*$//'))
> compadd -ld change_descriptions -a reply
> compstate[list]='list force'
>}
This one works perfectly.
Thanks!
--
Cesar Augusto Rorato Crusius o _ _ _
Stanford University __o /\_ _ \\o (_)\__/o (_)
e-mail:crusius@barcelonadesign.com _`\<, _>(_) (_)/<_ \_| \ _|/' \/
www.stanford.edu/~crusius (_)/(_) (_) (_) (_) (_)' _\o_
He who sacrifices functionality for ease of use
Loses both and deserves neither
next reply other threads:[~2001-05-29 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 15:41 Cesar Crusius [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-25 15:17 Cesar Crusius
2001-05-24 18:44 Cesar Crusius
2001-05-25 14:26 ` 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=E154lcS-0004Z0-00@sevilla \
--to=crusius@barcelonadesign.com \
--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).