From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Wayne Davison <wayned@users.sourceforge.net>,
Zsh Workers <zsh-workers@sunsite.auc.dk>
Subject: Re: A couple completion glitches
Date: Sat, 24 Jun 2000 23:21:23 +0000 [thread overview]
Message-ID: <1000624232123.ZM16787@candle.brasslantern.com> (raw)
In-Reply-To: <1000624230022.ZM16742@candle.brasslantern.com>
On Jun 24, 11:00pm, I wrote:
}
} Hmm; looks like there's a bug in `zstyle -T', though I have no idea how
} that crept in. Look here:
}
} zagzig% zstyle -L
} zstyle ':completion:*' completer _expand _complete
} zstyle ':completion:*:expand:*' suffix yes
} zagzig% zstyle -t :completion::expand::: suffix && echo suffix is set
} suffix is set
} zagzig% zstyle -T :completion::expand::: suffix && echo suffix not set
} suffix not set
}
} It shouldn't be possible for them both to return true.
Of course, I'm silly. It certainly should be possible for both to return
true. I keep forgetting that the difference between -t and -T is how they
treat the case of the style NOT being set, not how they treat it when it
IS set.
So in fact for the original question:
} } % touch foo{1..3}
} } % ls ~/foo*<tab>
} }
} } ...and nothing happens!
You DO need to set the suffix style, but you need to set it to "false".
Which, now that I think about it, sounds backwards to me. It means "do
not make a special case of expansions that have a suffix" but it *seems*
to mean "do not expand the suffix." Which is how I got confused about
what _expand was testing with "zstyle -T" in the first place ...
--
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-06-24 23:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-24 19:54 Wayne Davison
2000-06-24 23:00 ` Bart Schaefer
2000-06-24 23:21 ` Bart Schaefer [this message]
2000-06-25 8:38 ` Wayne Davison
2000-06-25 17:01 ` Bart Schaefer
2000-06-25 2:21 ` 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=1000624232123.ZM16787@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=wayned@users.sourceforge.net \
--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).