Re: History bug in zsh 5.0.5

[Axel Beckert <abe@xxxxxxxxxxxxxxx>]

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@xxxxxxxxxxxxxxx  (Mail)
 X   See http://www.nonhtmlmail.org/campaign.html | abe@xxxxxxxxx (Mail+Jabber)
/ \  I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)