From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Calling completion function from a non-completion ZLE widget
Date: Tue, 30 May 2000 07:20:18 +0000 [thread overview]
Message-ID: <1000530072019.ZM22395@candle.brasslantern.com> (raw)
I accidentally ended up with a function bound to an ordinary widget (i.e.
zle -N ...) that called _complete_help. [*] Bad, very bad. Not only did
it complain:
_main_complete:compset:52: can only be called from completion function
_default:compcall:12: can only be called from completion function
_main_complete:266: bad set of key/value pairs for associative array
But now that shell is also in a state where no completion of any kind does
anything other than beep at me and occasionally spit out errors about
bad math expressions, like this:
zstyle:5: bad math expression: operand expected at `:completio...'
Hmm, I suspect _complete_help got aborted in progress by one of the above
errors and left some functions defined. Yup, that's it; probably left
some other garbage state as well. Yow, it even left $compstate in an
inconsistent state! $+compstate is 1, $#compstate is also 1, but trying
`typeset | grep ^compstate` yields nothing.
It'd be best if that sort of thing doesn't happen, but there's no way to
trap on only the sort of error that causes the whole call stack to abort
(as `bad set of ...' seems to have).
The best we can do seems to be a bit of defensive programming up front.
What's a reliable way to determine that the completion system is active?
(Testing a parameter won't do it, the user could always set another of
the same name.)
[*] It should have been calling `zle _complete_help', I forgot the `zle'.
--
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 reply other threads:[~2000-05-30 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-30 7:20 Bart Schaefer [this message]
2000-05-30 7:59 Sven Wischnowsky
2000-05-30 15:38 ` 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=1000530072019.ZM22395@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).