From: "E. Jay Berkenbilt" <ejb@ql.org>
To: schaefer@candle.brasslantern.com
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: parse errors and up-line-or-history
Date: Tue, 17 Oct 2000 19:03:57 -0400 [thread overview]
Message-ID: <200010172303.TAA15698@soup.ql.org> (raw)
In-Reply-To: <001017142111.ZM3802@candle.brasslantern.com> (schaefer@candle.brasslantern.com)
> > zsh% for in *; do echo $i; done
> > zsh: parse error near `do'
> >
> > which seems entirely reasonable. If you then do ^p to fix it, you see
> > only
> >
> > zsh% for in *; do
> >
> > and not the whole command.
>
> Congratulations, you've revived the "literal vs. lexical history" debate,
> if it ever really was a debate.
>
> Zsh used to have an option to store the command history as the literal
> input text, rather than as lexical words. IIRC, it actually stored both
> and let you select which one to retrieve. The duplication was resolved
> in favor of lexical history a *very* long time ago, with the side-effect
> that anything that won't lex, doesn't make it into the history.
>
> For a partial workaround, see zsh-workers/10996.
This workaround does exactly what I want. I just bound your
zle-fetch-previous and zle-fetch-next to ^x^p and ^x^n respectively so
I get the benefits of the lexical history except when I really want
the other in which case I can specify it directly. Thanks.
Jay
next prev parent reply other threads:[~2000-10-17 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-17 19:35 E. Jay Berkenbilt
2000-10-17 21:21 ` Bart Schaefer
2000-10-17 23:03 ` E. Jay Berkenbilt [this message]
2000-10-18 9:08 ` Peter Stephenson
2000-10-18 15:38 ` Bart Schaefer
2000-10-19 7:10 ` Wayne Davison
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=200010172303.TAA15698@soup.ql.org \
--to=ejb@ql.org \
--cc=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).