From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Dear old literal history
Date: Fri, 28 Apr 2000 08:32:31 +0000 [thread overview]
Message-ID: <1000428083231.ZM24404@candle.brasslantern.com> (raw)
Does anyone else ever get nostalgic for "literal history"? This used to be
turned on by `setopt HIST_LIT' (or `set -j' for those wondering why the
single-letter options skip from -i to -k). Occasionally this was useful if
one wrote a complicated history substitution which failed in some small way,
and one therefore wanted to edit the line from *before* history was expanded.
I was about to suggest that it would be pretty easy now to reinstate the
literal history via ZLE widgets, when I discovered by an accident of search
terms that I already did so back in zsh-workers/4269. Except that now it's
possible to do a much better job, and widgets don't work quite like they
did a year and a half ago anyway.
-------------------------------------------------------------------------
typeset -A zle_lines
typeset -i zle_hist
precmd() {
zle_hist=${(%%):-%h} # The one icky bit
((zle_hist > HISTSIZE)) && unset zle_lines\[$[zle_hist-HISTSIZE]\]
}
zle-store () {
zle_lines[$zle_hist]=$BUFFER
zle .accept-line
}
zle-fetch-previous () {
zle .up-history || return 1
(($+zle_lines[$HISTNO])) && BUFFER=$zle_lines[$HISTNO]
return 0
}
zle-fetch-next () {
NUMERIC=-${NUMERIC:-1}
zle-fetch-previous
}
zle -N zle-store
zle -N zle-fetch-next
zle -N zle-fetch-previous
zle -A zle-store accept-line
-------------------------------------------------------------------------
An exercise for someone (maybe me, not tonight): Implement LITHISTSIZE.
(That means one can't use .up-history and HISTNO, which gets ugly.)
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
reply other threads:[~2000-04-28 8:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1000428083231.ZM24404@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.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).