From: ruud grosmann <r.grosmann@gmail.com>
To: zsh-users@zsh.org
Subject: change behaviour of command line completion
Date: Wed, 27 May 2015 13:36:56 +0200 [thread overview]
Message-ID: <CA+chMgvdSfqBY6nimCJZLN0iH9SiTKqBtoFq51PuqQNdzCTBJA@mail.gmail.com> (raw)
hello all,
recently, I have changed to using ohmyzsh. I want to undo one of the
many changes, but I don't know what the change is caused by.
In the old situation, when I was in a directory with only one file,
'example.txt' and I typed 'ls x<TAB>', no completion followed. Because
no files start with an 'x'.
But now, zsh happily changes the x to 'example.txt', because the x is
in 'example.txt'. I rather don't want this behaviour, but I cannot
find in the documentation of the options anything that describes this.
I hope you can tell me what this (too) smart completion is caused by,
so that I can update my profile. If it is not controlled by an option,
I hope to find out what other possibilities van influence this kind of
behaviour...
I am running zsh 4.3.17 from the debian wheezy distribution.
When I use the ohmyzsh profile, the following options are added
compared to the old situation:
alwaystoend
autocd
cdablevars
extendedhistory
noflowcontrol
histexpiredupsfirst
histignorespace
histverify
longlistjobs
promptsubst
pushdignoredups
pushdminus
sharehistory
The correct option is not active any more.
thanks in advance, Ruud
next reply other threads:[~2015-05-27 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 11:36 ruud grosmann [this message]
2015-05-27 11:55 ` Peter Stephenson
2015-05-27 13:03 ` Peter Stephenson
2015-05-27 21:14 ` Andrew Janke
2015-05-28 8:15 ` ruud grosmann
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=CA+chMgvdSfqBY6nimCJZLN0iH9SiTKqBtoFq51PuqQNdzCTBJA@mail.gmail.com \
--to=r.grosmann@gmail.com \
--cc=zsh-users@zsh.org \
/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).