From: Wayne Davison <wayned@users.sourceforge.net>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-users@sunsite.auc.dk
Subject: Re: configuring the new completion system
Date: Tue, 6 Jun 2000 23:03:54 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0006062243460.11477-100000@phong.blorf.net> (raw)
In-Reply-To: <1000607052651.ZM4901@candle.brasslantern.com>
On Wed, 7 Jun 2000, Bart Schaefer wrote:
> I think you want to NOT rebind '\t' to complete-word -- that is,
> leave it bound to expand-or-complete -- AND leave out the _expand
> completer. This will give you the old behavior of expansion
> followed by the new behavior of completion.
That would be cool if I could get it to work. However, no matter
what I try, tab does not expand wildcards with expand-or-complete
set. It just expands $VARIABLES.
> You can still get the new behavior of _expand from <C-x e> in this case.
The only thing I get when I do that is this error:
_expand_word:5: curcontext: parameter not set
This is caused by my predilection to having the "no_unset" option set
for my interactive-shell use. Seems like this should get turned off
when the shell runs some completion/expansion code. Do we have an
existing solution for such things?
When I "setopt unset", then the <C-x e> binding is quite handy. If I
could just re-introduce those old changes to have it stop expanding
tildes, I'd be quite happy.
..wayne..
prev parent reply other threads:[~2000-06-07 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-06 1:07 blah*[TAB] (difference between 3.1.6 and 3.1.9) Vincent Lefevre
2000-06-06 3:20 ` Bart Schaefer
2000-06-06 9:22 ` Vincent Lefevre
2000-06-06 22:22 ` configuring the new completion system Wayne Davison
2000-06-07 5:26 ` Bart Schaefer
2000-06-07 6:03 ` Wayne Davison [this message]
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=Pine.LNX.4.21.0006062243460.11477-100000@phong.blorf.net \
--to=wayned@users.sourceforge.net \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-users@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).