From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: $modules (was: Re: Seg fault with zmodload -u)
Date: Wed, 16 Aug 2000 11:56:44 +0200 (MET DST) [thread overview]
Message-ID: <200008160956.LAA11550@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Wed, 16 Aug 2000 10:45:05 +0100
Peter Stephenson wrote:
> Sven wrote:
> > Oliver Kiddle wrote:
> > > On the subject of zmodload completion, how would I prevent the 'module
> > > alias' description from being displayed when there are no module
> > > aliases - do I have to put the zmodload -A output in an array first and
> > > then not call the _requested line if the array is empty - or is there a
> > > better way?
> >
> > Eh? The description for the aliases should not be displayed when there
> > are no matches added for it (or none of the strings added for it match
> > what's on the line). Automatically. And it works for me (using a
> > simple test completion function).
>
> I had the same experience as Oliver before I changed _zmodload. Could it
> make a difference if the string on the line is empty? Or that I have
> different match groups listed separately?
No. It's that without aliases, `zmodload -A' prints a newline. I.e.,
one line. So `${${(f)"$(zmodload -A)"}%% *}' produces one string (an
empty one). This could have been fixes by using:
`${${${(f)"$(zmodload -A)"}%% *}:#}'.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-08-16 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-16 9:56 Sven Wischnowsky [this message]
2000-08-16 10:12 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
2000-08-16 10:34 Sven Wischnowsky
2000-08-16 9:23 Sven Wischnowsky
2000-08-16 9:45 ` Peter Stephenson
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=200008160956.LAA11550@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).