help / color / mirror / code / Atom feed
From: "Andreas Kusalananda Kähäri" <andreas.kahari@abc.se>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-users@zsh.org
Subject: Re: Repeating last command from *local* history
Date: Sun, 28 Feb 2021 14:25:45 +0100	[thread overview]
Message-ID: <20210228132545.GA76759@box.prefix.duckdns.org> (raw)
In-Reply-To: <27299937c9c060b1a8ed1acbce6cda5c72d63a64.camel@ntlworld.com>

On Thu, Feb 11, 2021 at 08:47:46PM +0000, Peter Stephenson wrote:
> On Thu, 2021-02-11 at 17:37 +0100, Andreas Kusalananda Kähäri wrote:
> > I'm using zsh 5.8 on OpenBSD 6.8, and I set the SHARE_HISTORY and
> > EXTENDED_HISTORY shell options.
> > 
> > I would like to repeat the last command from the command line history
> > of the current shell session, without accidentally executing a recent
> > command from some other shell session that I'm using in another
> > terminal.
> > 
> > Using "r -L" works, but only if the most recent command in the shared
> > history is a command from the current shell session.  If it isn't, the
> > shell responds with "fc: no matching events found".
> > 
> > This *feels* like a bug.
> Yes, it's a typical "computer says no" bug.
> I thin this one's easy, although it's possible there are more implications
> here than I'm picking up...
> pws

The patch seems to have made it into the zsh Git repository.  I've
re-built the shell from there and "r -L" now seems to work the way I was
initially expecting it to work.  Thanks for this!


Andreas (Kusalananda) Kähäri
SciLifeLab, NBIS, ICM
Uppsala University, Sweden


      reply	other threads:[~2021-02-28 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 16:37 Andreas Kusalananda Kähäri
2021-02-11 20:47 ` Peter Stephenson
2021-02-28 13:25   ` Andreas Kusalananda Kähäri [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210228132545.GA76759@box.prefix.duckdns.org \
    --to=andreas.kahari@abc.se \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=zsh-users@zsh.org \


* 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


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).