From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Vincent Lefevre <vincent@vinc17.org>, zsh-users@sunsite.auc.dk
Subject: Re: blah*[TAB] (difference between 3.1.6 and 3.1.9)
Date: Tue, 6 Jun 2000 03:20:38 +0000 [thread overview]
Message-ID: <1000606032038.ZM25884@candle.brasslantern.com> (raw)
In-Reply-To: <20000606030750.A12454@vin.ens-lyon.fr>
On Jun 6, 3:07am, Vincent Lefevre wrote:
} Subject: blah*[TAB] (difference between 3.1.6 and 3.1.9)
}
} Consider a directory where there are two files blah1 and blah2. With
} zsh 3.1.6, when I typed blah* followed by a tab, "blah1 blah2 " was
} generated (with a space after blah2). With zsh 3.1.9, "blah1 blah2"
} is generated (with *no* space after blah2).
}
} How can I have the old behavior (much more logical IMHO)?
Something's definitely gone wrong with expand-or-complete. This was not
intentional.
As a workaround, the following should behave the way you want:
bindkey '\t' complete-word
autoload -U compinit
compinit
zstyle ':completion:*' completer _expand _complete
zstyle ':completion:*:expand:::' glob 1
zstyle ':completion:*:expand:::' substitute 1
If you have some customized compctl commands, you may also want:
zstyle ':completion:*' use-compctl 1
The above consititutes pretty much the minimal set of commands to emulate
the default behavior of expand-or-complete in 3.1.6 and earlier versions
while using the new completion system.
--
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-06 3:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-06 1:07 Vincent Lefevre
2000-06-06 3:20 ` Bart Schaefer [this message]
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
2000-06-06 9:20 blah*[TAB] (difference between 3.1.6 and 3.1.9) 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=1000606032038.ZM25884@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=vincent@vinc17.org \
--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).