From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Styles that aren't :completion:* ...
Date: Tue, 16 May 2000 15:05:06 +0000 [thread overview]
Message-ID: <1000516150506.ZM23747@candle.brasslantern.com> (raw)
In-Reply-To: <200005160758.JAA19581@beta.informatik.hu-berlin.de>
On May 16, 9:58am, Sven Wischnowsky wrote:
} Subject: Re: Styles that aren't :completion:* ...
}
} Bart Schaefer wrote:
}
} > I notice that the nslookup function uses a context of ':nslookup', whereas
} > assorted zftp components use ":zftp$curcontext".
}
} Yes, but it's not the completion-$curcontext, it's the zftp-one.
Ah.
} I considered i-complete-w to be a completion thing. And since in
} completion it uses `:completion:incremental:...' I thought it would be
} easier to understand if it used that for all styles.
Yes, that's what I'm struggling with here. One question is, is there any
way $curcontext could have a value at the time i-c-w or i-a-p are called?
They'd have to be getting called *inside* the completion or zftp systems,
wouldn't they? Which they shouldn't ... so it doesn't make sense to e.g.
zstyle ':completion:predict:*:-math-:*' cursor complete
zstyle ':completion:predict:*' cursor key
because insert-and-predict doesn't know that it's in math context. (On
the other hand, it might be nice to be able to do that ...)
But it's still necessary to at least set curcontext=predict::: so that the
right function field will be present when `zle complete-word' is called.
} > What's the context?
}
} `:predict', I'd say.
Then we'll have to remove the i-c-w and predict documentation from the
completion system sections. Where should it go instead?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-05-16 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-16 7:58 Sven Wischnowsky
2000-05-16 15:05 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-17 6:41 Sven Wischnowsky
2000-05-16 6:28 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=1000516150506.ZM23747@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).