From: John Covici <covici@ccs.covici.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh-users@zsh.org
Subject: Re: history substring search too aggressive sometimes
Date: Wed, 31 Aug 2016 08:33:02 -0400 [thread overview]
Message-ID: <m3a8ftqfsx.wl-covici@ccs.covici.com> (raw)
In-Reply-To: <20160831121025.14c1c869@pwslap01u.europe.root.pri>
On Wed, 31 Aug 2016 07:10:25 -0400,
Peter Stephenson wrote:
>
> On Wed, 31 Aug 2016 07:03:58 -0400
> John Covici <covici@ccs.covici.com> wrote:
> > Well, I was looking at the options section of the manual, and
> > although its not perfect yet, disabling menucomplete which was on and
> > complete_in_word, helped a great deal. Also, I discovered to get a
> > list of all the options, I had to do
> > set -o
> > instead of setopt which I was doing before.
>
> Hmm, setopt should show you all non-default options, so if menucomplete
> was on it should show up. That explains why you're getting the first
> word inserted.
>
> complete_in_word is only applied if the cursor is in the middle of the
> word when you hit tab, and only at that point. (The standard assumption
> is you're at the end of the word you're completing, but it should
> be possible to get it to work anyway.)
>
> None of the other options look relevant.
>
> Note there are additional extra things going on if you have directory
> paths as it will complete multiple components, but it didn't sound like
> that was the issue.
>
OK. I think I am on the road for a solution here, thanks a lot.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
prev parent reply other threads:[~2016-08-31 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 12:29 John Covici
2016-08-30 19:49 ` Peter Stephenson
2016-08-30 21:09 ` John Covici
2016-08-31 9:08 ` Peter Stephenson
2016-08-31 11:03 ` John Covici
2016-08-31 11:10 ` Peter Stephenson
2016-08-31 12:33 ` John Covici [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=m3a8ftqfsx.wl-covici@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=p.stephenson@samsung.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).