zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: command recall
Date: Sun, 7 Feb 2021 10:09:44 -0800	[thread overview]
Message-ID: <8e1a7c38-1901-0085-88e4-96b3acc208be@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7aqLVodpU1zHh2Mt0=iEkr4dpU5Fno565WU38w==zLvkA@mail.gmail.com>

On 2021-02-07 8:56 a.m., Bart Schaefer wrote:

> ... There are all sorts of reasons for
> this, including being able to have a stable numbering scheme (keys in
> the $history hash table) during computation of zle widgets.
I wondered how that worked.  With half a dozen open terminals, each of 
them accepting
commands at various times, it's quite cool how they all end up in 
chronological order when
merged.  I've tried all sorts of ways to break that but it refuses to be 
fooled.
>
> That's because the order of operations is
> 1) You accept-line, so the pinocchio entry is ready to become a real boy
> 2) Consequently, the history gets merged
> 3) The "history" command executes
This is the tiniest of issues but I was just about to start 
experimenting with making
a widget, which I did once and it worked.  If you had:

....
accept-line
history-beginning-search-backward
....

would that work?  Probably some easy way to force the merge before the 
search, no?
Still it seems intuitive that this should happen anyway.





  reply	other threads:[~2021-02-07 18:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06 16:36 Ray Andrews
2021-02-06 17:10 ` Lawrence Velázquez
2021-02-06 17:22   ` Lawrence Velázquez
2021-02-06 22:08     ` Bart Schaefer
2021-02-06 23:11       ` Ray Andrews
2021-02-07 16:56         ` Bart Schaefer
2021-02-07 18:09           ` Ray Andrews [this message]
2021-02-07 20:42             ` Bart Schaefer
2021-02-07 21:34               ` Ray Andrews
2021-02-07 19:12 ` Bart Schaefer

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=8e1a7c38-1901-0085-88e4-96b3acc208be@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).