From: Eike Kroemer <kroemer@atlas.de>
To: zsh-users@sunsite.dk
Subject: what zshcompsys-syntax is equals compctl -C -f ?
Date: Fri, 04 Nov 2005 10:34:09 +0100 [thread overview]
Message-ID: <436B2B11.1070503@atlas.de> (raw)
Hi there,
just recently I had to upgrade from zsh 4.0.6 to zsh 4.2.1 and now I'm
unable to reproduce the filename-completion behaviour I'm used to.
My old .zshrc had the lines
-------------------------------->
#### options for zsh-behaviour
setopt always_to_end
setopt auto_list
unsetopt automenu
setopt auto_param_slash
setopt bsd_echo
setopt csh_null_glob
setopt extended_glob
unsetopt menu_complete
unsetopt rec_exact
setopt no_nomatch
setopt rmstarsilent
setopt sh_file_expansion
setopt nocorrect
setopt nocorrect_all
unsetopt auto_remove_slash
# expand only to filenames
compctl -C -f
--------------------------------<
and I used "compctl -C -f" to avoid path-lookup in completion.
For example assume my $PWD has a subdirectory "bin/" and I want to call
"Script" located in this dir.
As long as compctl -C -f worked I could enter "bi<tab>" and zsh would
expand to bin/, the only file or directory starting with "bi" present in
$PWD.
But now that compctl is deprecated I'm unable to configure the new-style
behaviour of zshcompsys to reproduce the desired result.
Default-behaviour is to include all executables in $PATH beginning with
"bi", sadly yielding
kroemer@pcma44:~ > bi<tab>
bibtex bindkey bioradtopgm bitmap
bin/ binhex bison
which is of no use to me :-(
Can anyone help?
Thanks in advance....
Eike
--
"...but plagiarize, plagiarize, plagiarize,
only be sure to always call it please -- research"
(Tom Lehrer: Lobachevsky)
next reply other threads:[~2005-11-04 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 9:34 Eike Kroemer [this message]
2005-11-04 10:21 ` DervishD
2005-11-04 10:33 ` Peter Stephenson
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=436B2B11.1070503@atlas.de \
--to=kroemer@atlas.de \
--cc=zsh-users@sunsite.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).