zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Zsh workers <zsh-workers@zsh.org>
Subject: Re: Finding the first history event of the current instance
Date: Sun, 31 May 2015 11:29:24 +0200	[thread overview]
Message-ID: <12467.1433064564@thecus.kiddle.eu> (raw)
In-Reply-To: <150530154236.ZM17511@torch.brasslantern.com>

Bart wrote:
> } Or there's this patch.  I didn't add an option for listing only the

I know I've missed fc's ability to do this so that definitely looks
useful.

When it gets finalised, don't forget _fc.

> The options -N (new), -O (old), and -F (foreign) are all currently unused
> by "fc" if we wanted to add multiple filterings.

I think I'd favour +L for foreign (i.e. not local). It's easier to
remember that way. I'm not sure how the option parser works but that may
change the meaning of fc + which isn't ideal.

Rather than using the HIST_OLD or whatever flags, is it possible to
instead identify what the history number was when the shell started?

For new/old, one option would be to have a special token such as "-",
".", "^" or "0" that can be used to indicate the history number
when the shell started. It might need to be inclusive when used at the
start of the range and exclusive when used at the end so not exactly the
same as the number. So for example, this would be all old:
  fc -l 1 -
And this would be all new:
  fc -l -
Admittedly, this doesn't allow you to get a history entry matching a
pattern from the old entries.

Oliver


       reply	other threads:[~2015-05-31  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r3q7nzkr.fsf@gmail.com>
     [not found] ` <150529171657.ZM15077@torch.brasslantern.com>
     [not found]   ` <150530154236.ZM17511@torch.brasslantern.com>
2015-05-31  9:29     ` Oliver Kiddle [this message]
2015-05-31 23:59       ` Bart Schaefer
2015-06-01  1:50         ` Mikael Magnusson
2015-06-01  4:02           ` Bart Schaefer
     [not found] ` <150529171657.ZM15077__24226.5334389687$1432945137$gmane$org@torch.brasslantern.com>
2015-06-05  8:47   ` Christian Neukirchen
2015-06-06 16:54     ` 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=12467.1433064564@thecus.kiddle.eu \
    --to=okiddle@yahoo.co.uk \
    --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).