zsh-workers
 help / color / mirror / code / Atom feed
From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Re: History bug in zsh 5.0.5
Date: Wed, 4 Jun 2014 17:09:42 +0200	[thread overview]
Message-ID: <20140604150941.GL7931@sym.noone.org> (raw)
In-Reply-To: <140604075559.ZM30360@torch.brasslantern.com> <8020140C-4E21-4136-BA9B-D258065847E5@gmail.com>

Hi Bart,

On Wed, Jun 04, 2014 at 11:36:47AM +0400, RoboSloNE wrote:
> I found this bug in latest zsh (I’ve not tried git version yet):
> incremental history doesn’t work right after command is executed, it
> waits for the next command to log first one.
> 
> > How to reproduce:
> > 1. Enable this options in ~/.zshrc: extended_history, inc_append_history, share_history
> > 2. Restart shell
> > 3. Open two tabs (shells)
> > 4. Type 'echo 123' in first shell
> > 5. Press Ctrl+R in second shell: 'echo 123' is not in history
> > 6. Just press enter
> > 7. CTRL+R, and you'll see the updated list

On Wed, Jun 04, 2014 at 07:55:59AM -0700, Bart Schaefer wrote:
> This has already been reported and a patch can be found in the article
> zsh-workers/32682 ( http://www.zsh.org/mla/workers/2014/msg00470.html )
> 
> It was an intentional change to fix a different problem (elapsed time
> accuracy) but we underestimated the importance for some users of having
> the immediate file update.

Are you sure these are the same things? I'm not.

But I thought so first, too. :-) There's no sleep or such in
RoboSloNE's report and it's about SHARE_HISTORY which
zsh-workers/32682 isn't (IIRC).

I think he rather argues, that Ctrl-R should already reread the
history from disk and not only the next command (or an empty command
by just pressing enter).

		Kind regards, Axel
-- 
/~\  Plain Text Ribbon Campaign                   | Axel Beckert
\ /  Say No to HTML in E-Mail and News            | abe@deuxchevaux.org  (Mail)
 X   See http://www.nonhtmlmail.org/campaign.html | abe@noone.org (Mail+Jabber)
/ \  I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)


  parent reply	other threads:[~2014-06-04 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  7:36 RoboSloNE
2014-06-04 14:55 ` Bart Schaefer
2014-06-04 15:09 ` Axel Beckert [this message]
2014-06-04 15:26   ` Peter Stephenson
2014-06-04 16:22   ` 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=20140604150941.GL7931@sym.noone.org \
    --to=abe@deuxchevaux.org \
    --cc=zsh-workers@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).