From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh users <zsh-users@sunsite.dk>
Subject: Re: history expansion
Date: Thu, 26 Sep 2002 17:05:47 +0000 [thread overview]
Message-ID: <1020926170547.ZM1625@candle.brasslantern.com> (raw)
In-Reply-To: <20020926101224.GA30361@freepuppy.bellavista.cz>
On Sep 26, 12:12pm, Roman Neuhauser wrote:
} Subject: Re: history expansion
}
} > } % !!:s/!!3/!-2:s,foo,bar,/
}
} > There isn't any option or other setting that allows history expansions
} > to be nested in that way.
}
} not knowing the internals of the history expansion, what is the
} probability of nested expansion appearing in zsh?
On Sep 26, 11:28am, Peter Stephenson wrote:
}
} It doesn't look *that* difficult, but it's not completely trivial (some
} of the state is currently kept in global variables) so it's a bit of
} work
In particular I'm concerned about the default (non-CSH_JUNKIE) history
behavior:
By default, a history reference with no event designator refers to the
same event as any preceding history reference on that command line; if
it is the only history reference in a command, it refers to the previous
command.
Within a nested expression, which references "precede" which others? If yet
another history reference follows (in a separate word) a nested reference,
which of the subexpressions of the nested reference determines which event
is used by that second reference?
(If this thread continues, it should be moved to zsh-workers.)
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2002-09-26 17:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 10:33 Roman Neuhauser
2002-09-25 23:43 ` Bart Schaefer
2002-09-26 10:12 ` Roman Neuhauser
[not found] ` <20465.1033036099@csr.com>
2002-09-26 17:05 ` Bart Schaefer [this message]
2002-09-26 17:32 ` Roman Neuhauser
-- strict thread matches above, loose matches on Subject: below --
2020-02-20 12:44 Pier Paolo Grassi
2020-02-20 13:05 ` Vin Shelton
2020-02-20 13:19 ` Pier Paolo Grassi
2020-02-20 13:25 ` Vin Shelton
2020-02-20 13:29 ` Pier Paolo Grassi
2020-02-20 15:25 ` Mikael Magnusson
2020-02-20 15:31 ` Pier Paolo Grassi
2020-02-21 22:50 ` gi1242+zsh
2020-02-22 0:21 ` Pier Paolo Grassi
2020-02-22 0:36 ` Bart Schaefer
2020-02-22 1:01 ` Pier Paolo Grassi
2002-04-30 16:33 Roman Neuhauser
2002-04-30 16:43 ` Bart Schaefer
2002-05-06 12:51 ` Roman Neuhauser
2002-05-06 12:43 ` Borsenkow Andrej
2002-05-06 13:11 ` Roman Neuhauser
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=1020926170547.ZM1625@candle.brasslantern.com \
--to=schaefer@brasslantern.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).