From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Why does ^X? behave differently than TAB?
Date: Wed, 17 May 2000 09:46:06 +0000 [thread overview]
Message-ID: <1000517094606.ZM11120@candle.brasslantern.com> (raw)
This situation is a little baroque; I'm not sure I can give a simple case
that reproduces it.
I have a script that uses a `select' loop, and I want completion at the
prompt. So I did this inside the script:
local curcontext=scriptname:::
zstyle ':completion:scriptname:*' insert-tab no
zstyle ':completion:scriptname:*' completer _script_completer
_script_completer() { compcall -T -D }
The reason for the compcall is that this is an old script that uses a trick
with compctl -T to force 3.0.x to complete something other than commands at
the select prompt:
l=(list of things to complete)
compctl -Tx 'p[1,-1]' -f - 'W[0,*]' -k l ${${ZSH_VERSION##3.0*}:+-tn}
I.e., complete from $l in the first word, otherwise complete file names.
This all works fine as long as I never press anything but TAB for completion;
it even starts up menu-selection properly based on my other styles, etc.
However, if at any point after the first TAB, I press ^X? (_complete_debug)
instead, I get command completion (which usually means a menu-select with
2198 choices, but sometimes it just asks if I really want to see all 2198
possibilities).
I would just write this off as a new/old completion incompatibility if not
for the fact that it differs depending on the widget used to activate the
completion. And if I replace the `compcall' with `compadd $l' then it works
(except for not completing files) with any combination of TAB and ^X?.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next reply other threads:[~2000-05-17 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-17 9:46 Bart Schaefer [this message]
2000-05-17 13:11 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=1000517094606.ZM11120@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).