From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: _expand, _expand_word, and their doc
Date: Thu, 5 Oct 2000 10:13:02 +0200 (MET DST) [thread overview]
Message-ID: <200010050813.KAA12647@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Wed, 20 Sep 2000 17:57:16 +0000
Bart Schaefer wrote:
> ...
>
> Then, there was a completely inaccurate remark about the expansions and
> all-expansions tags in the doc: They're *not* available when using the
> completions style with _expand. If that's a bug in _expand rather than
> in the doc, I can't immediately see how to fix it ... so I changed the
> doc, and maybe Sven will do something to _expand when he returns.
I stumbled over this, too, when reading the manual while I was away.
I don't see a way to implement such a behaviour (i.e. I'm pretty sure
it isn't possible currently). So, Bart's changes, both in the docs and
in _expand(|_word) are fine.
But of course I may start to think if this could be implemented -- if
I find a not-too-complicated way for changing the C-code...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-10-05 8:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-05 8:13 Sven Wischnowsky [this message]
2000-10-05 15:21 ` Bart Schaefer
2000-10-05 15:34 ` Andrej Borsenkow
2000-10-05 17:11 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2000-10-09 11:49 Sven Wischnowsky
2000-10-06 8:14 Sven Wischnowsky
2000-10-06 12:34 ` Andrej Borsenkow
2000-10-06 13:00 ` Sven Wischnowsky
2000-10-08 19:35 ` Bart Schaefer
2000-09-20 17:57 Bart Schaefer
2000-09-21 5:07 ` Bart Schaefer
2000-09-21 6:33 ` Andrej Borsenkow
2000-09-21 14:37 ` Bart Schaefer
2000-09-21 14:59 ` Andrej Borsenkow
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=200010050813.KAA12647@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).