From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: make history-complete-older do nothing on empty string
Date: Thu, 3 Dec 2037 04:10:39 -0800 [thread overview]
Message-ID: <c012d701-ebc5-df2a-ab6d-7dc34292fa45@eastlink.ca> (raw)
In-Reply-To: <m31sfbvj8r.fsf@luffy.cx>
On 18/04/18 10:49 PM, Vincent Bernat wrote:
> ❦ 18 avril 2018 11:53 -0700, Ray Andrews <rayandrews@eastlink.ca> :
>
>>>> Vincent, what version of zsh are you running? There were some memory
>>>> management optimizations done in the past year or so that might speed
>>>> up large history accesses in general.
>>> FI, it is 5.5.1. And HISTFILE is set to 20000 (since years).
>> Just curious: Why would completion on an empty string everbe useful?
> Dunno. I want it to do nothing too if that's what you are asking.
Yeah. It seems to me that the thing would/should know that it has
nothing to do. It's sorta like writing a program to find the first
prime number divisible by two, the program will run for a long time
without producing much. I'm wondering if the devs just overlooked that,
or if perhaps the idea of completion on an empty string might actually
have some sort of meaning. Completion seems to be such a complex thing
that maybe it does -- the sound of one hand clapping.
next prev parent reply other threads:[~2018-04-19 16:09 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
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 [this message]
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=c012d701-ebc5-df2a-ab6d-7dc34292fa45@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).