From: Mikael Magnusson <mikachu@gmail.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: suffixes in _zstyle, was: How to accept a completion?
Date: Tue, 12 Jan 2010 23:39:15 +0100 [thread overview]
Message-ID: <237967ef1001121439q1e10a3d7h24a2dffc0156bb57@mail.gmail.com> (raw)
2009/4/29 Mikael Magnusson <mikachu@gmail.com>:
> 2009/3/19 Peter Stephenson <pws@csr.com>:
>> Mikael Magnusson wrote:
>>
>>> As an aside, after i write $PWD(:<tab> to get the s, how do i "accept"
>>> the completion to make tab complete the - instead of cycling to the
>>> next completer? The only way i found is typing something and deleting
>>> it... When completing directories i usually just type a /.
>>
>> Just type the string that's got to come next; it always does, or the s
>> is useless: there's no point typing anything you need to delete, just
>> use what you don't need to delete. Actually, why don't you just type
>> "s-"? The "completion" is really only there as a mnemonic of what can
>> go at that point, it doesn't save you any typing even in the optimal
>> case.
>
> Okay, finally encountered a real example of this being annoying now.
> % scp file lt<tab>
> ---- file
> lth/
> ---- remote host name
> lth
>
> tabbing to the remote host name gives me
> % scp file lth:
> Now how do i complete files on the remote end? If i press tab again i just get
> % scp file lth/
> And if i type a : i get
> % scp file lth::
> the only way that works is typing something and backspacing, then
> pressing tab again...
Found another one of these, zstyle <tab><tab> gives you :completion:
with no obvious way to continue completing without <space><backspace>
or some variation thereof. The following fixes it; I think this is
another case of not wanting the : to be removed on a space, but the
rest of the completer uses -qS.
I did notice though that my "hilight suffixes" thing only works for
the -q case, not for -r:, same with the scp completion. I was really
just looking around at various variables in that code picking one that
seemed to be what I wanted, but apparently I didn't get the exact
correct thing then. Any ideas?
--
Mikael Magnusson
diff --git a/Completion/Zsh/Command/_zstyle b/Completion/Zsh/Command/_zstyle
index 0080619..6e34fcc 100644
--- a/Completion/Zsh/Command/_zstyle
+++ b/Completion/Zsh/Command/_zstyle
@@ -185,7 +185,7 @@ while (( $#state )); do
case "$state[1]" in
(contexts)
if [[ ! -prefix :*: ]]; then
- _wanted contexts expl context compadd -P : -S : completion zftp
+ _wanted contexts expl context compadd -P : -qS : completion zftp
elif compset -P :completion:; then
for ostate in functions _completers cmdorcont argument tag; do
compset -P '[^:]#:' || break
reply other threads:[~2010-01-12 22:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=237967ef1001121439q1e10a3d7h24a2dffc0156bb57@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=zsh-workers@zsh.org \
/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).