From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>,
<zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: _expand, _expand_word, and their doc
Date: Thu, 21 Sep 2000 14:37:40 +0000 [thread overview]
Message-ID: <1000921143740.ZM7186@candle.brasslantern.com> (raw)
In-Reply-To: <000201c02395$cf594fd0$21c9ca95@mow.siemens.ru>
On Sep 21, 10:33am, Andrej Borsenkow wrote:
} Subject: RE: PATCH: _expand, _expand_word, and their doc
}
} > +inserted into the command line. This style is most useful when set
} > +only for very specific completion contexts.
}
} I continue to ask myself just how useful it is.
I suspect it's intended to be used in the :completion:expand-word:expand::
context, though I didn't realize the context never gets any more specific
than that. That way the user can decide whether to invoke it.
If it would work to set compstate[insert]=all inside _expand_word, before
calling _main_complete, then we could do that instead and remove the
handling for that style from _expand. I don't have time today to try
this.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-09-21 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2000-09-21 14:59 ` Andrej Borsenkow
2000-10-05 8:13 Sven Wischnowsky
2000-10-05 15:21 ` Bart Schaefer
2000-10-05 15:34 ` Andrej Borsenkow
2000-10-05 17:11 ` Bart Schaefer
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-10-09 11:49 Sven Wischnowsky
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=1000921143740.ZM7186@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--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).