From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Styles that aren't :completion:* ...
Date: Tue, 16 May 2000 06:28:18 +0000 [thread overview]
Message-ID: <1000516062819.ZM23429@candle.brasslantern.com> (raw)
I notice that the nslookup function uses a context of ':nslookup', whereas
assorted zftp components use ":zftp$curcontext".
Yet incremental-complete-word uses ":completion:incremental${curcontext#*:}"
and similarly insert-and-predict uses ":completion:predict${curcontext#*:}".
So these functions actually strip off part of the context and replace it.
What's the idiom supposed to be, again?
Here's the specific reason that I ask: I'm thinking of adding some more
styles to predict-on/off and to the functions they bind to keystrokes. For
example, there's a comment in delete-backward-and-predict to the effect
that some people might prefer that it call predict-off. That seems like
an ideal thing to control with a style, but it feels funny to use a style
that starts with ":completion:" because no completion is happening during
delete-backward-and-predict.
Similarly I was thinking of adding a "verbose" style to predict-on, to have
it call "zle -M" when prediction goes into effect. That's called directly
from a keystroke. What's the context?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next reply other threads:[~2000-05-16 6:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-16 6:28 Bart Schaefer [this message]
2000-05-16 7:58 Sven Wischnowsky
2000-05-16 15:05 ` Bart Schaefer
2000-05-17 6:41 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=1000516062819.ZM23429@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).