zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-users@sunsite.dk
Subject: Re: !!:$
Date: Tue, 16 Nov 2004 16:08:02 +0000	[thread overview]
Message-ID: <200411161608.iAGG83Kh002893@news01.csr.com> (raw)
In-Reply-To: <20041116143144.GA23971@sc>

Stephane Chazelas wrote:
> Wouldn't it be the same as ${(%):-%!}?

Yes, except much more obvious.

Bart wrote:
> Umm.
> 
> HISTNO (integer)
>      The current history number.  Setting this has the same effect as
>      moving up or down in the history to the corresponding history line.
>      An attempt to set it is ignored if the line is not stored in the
>      history.
> 
> Admittedly this is available only in widgets, but it seems odd to have two
> variables for the same thing.

You didn't read down the patch far enough.

+history.  Note this is not the same as the parameter tt(HISTCMD),
+which always give the number of the history line being added to the main
+shell's history.  tt(HISTNO) refers to the line being retrieved within
+zle.

>> Then you can always get the full previous line as
>> $history[$((HISTCMD-1))].
>
> Unfortunately that doesn't always work.  If you setopt HIST_IGNORE_DUPS,
> $history[$((HISTNO-1))] may be empty.

That's a nuisance.  Maybe we need an ordinary array which always gives
the last items in the history, too.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


  reply	other threads:[~2004-11-16 16:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 13:45 !!:$ keef
2004-11-16 14:22 ` !!:$ Peter Stephenson
2004-11-16 14:31   ` !!:$ Stephane Chazelas
2004-11-16 15:37   ` !!:$ Bart Schaefer
2004-11-16 16:08     ` Peter Stephenson [this message]
2004-11-17  0:03 ` !!:$ Bart Schaefer
2004-11-17 19:25   ` !!:$ Danek Duvall
2004-11-18  1:10     ` !!:$ Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2018-02-19 21:12 &&|| Ray Andrews
2018-02-19 21:57 ` &&|| Peter Stephenson
2018-02-19 22:47   ` &&|| Ray Andrews
2018-02-20  9:26     ` &&|| Peter Stephenson
2018-02-20  7:54       ` &&|| Ray Andrews
2018-02-20 17:07         ` &&|| Peter Stephenson
2018-02-20 19:24           ` &&|| Ray Andrews
2018-02-20 20:28             ` &&|| Bart Schaefer
2018-02-20 21:45               ` &&|| Ray Andrews
2003-07-02 15:06 ?????? JEFF BICKLEY
2003-07-02 19:56 ` ?????? Thorsten Haude

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=200411161608.iAGG83Kh002893@news01.csr.com \
    --to=pws@csr.com \
    --cc=zsh-users@sunsite.dk \
    /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).