zsh-users
 help / color / mirror / code / Atom feed
From: Vincent Bernat <bernat@luffy.cx>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh-users@zsh.org
Subject: Re: make history-complete-older do nothing on empty string
Date: Wed, 18 Apr 2018 18:15:14 +0200	[thread overview]
Message-ID: <87fu3s4hkd.fsf@luffy.cx> (raw)
In-Reply-To: <20180418142845.1b473020@camnpupstephen.cam.scsc.local> (Peter Stephenson's message of "Wed, 18 Apr 2018 14:28:45 +0100")

 ❦ 18 avril 2018 14:28 +0100, Peter Stephenson <p.stephenson@samsung.com> :

>> So when you interrupted it it was apparently reading in 66742 history
>> words; there's nothing further at the end of the file?  (We can tweak
>> complete_debug to add timing info if it's helpful, see below.)
>
> Come to think of it, the fact that it's outputting all those words for
> debug purposes is going to make a big difference, so I'm not sure how
> much this is telling us.  If this turns out not to be the crucial point,
> we can disable debugging around it.

There was additional output, but I thought it was meaningless since I
think it shouldn't try to complete at all when the current word is
empty.

For the remaining:

http://paste.debian.net/1020908/

>
>> Is the behaviour acceptable if you use the style, for example:
>> 
>> zstyle ':completion:history-words:*' range 100
>> 
>> ?
>
> This should give some indication, though.

Yes, with this, it works fast. However, it doesn't use all history
anymore for regular completion. The search is done only on the last 100
items of the history. I would prefer to have complete completion when
there is at least one character in the current word and nothing when
not. I don't think people are interested to expand the empty word with
the content of the history.

In the meantime, this is a good workaround. Thanks!
-- 
It is a wise father that knows his own child.
		-- William Shakespeare, "The Merchant of Venice"


  reply	other threads:[~2018-04-18 16:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180418052832epcas2p1df623a44c88edae226f65a2d5edc90f2@epcas2p1.samsung.com>
2018-04-18  5:21 ` Vincent Bernat
2018-04-18  8:40   ` Peter Stephenson
2018-04-18  9:15     ` Vincent Bernat
2018-04-18  9:45       ` Peter Stephenson
2018-04-18 12:20         ` Vincent Bernat
2018-04-18 12:58           ` Peter Stephenson
2018-04-18 13:28             ` Peter Stephenson
2018-04-18 16:15               ` Vincent Bernat [this message]
2018-04-18 16:11             ` Bart Schaefer
2018-04-18 16:28               ` Vincent Bernat
2018-04-18 18:41               ` Vincent Bernat
2018-04-18 18:53                 ` Ray Andrews
2018-04-19  5:49                   ` Vincent Bernat
2037-12-03 12:10                     ` Ray Andrews
2037-12-03 14:36                       ` Ray Andrews

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=87fu3s4hkd.fsf@luffy.cx \
    --to=bernat@luffy.cx \
    --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).