From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: parse errors and up-line-or-history
Date: Wed, 18 Oct 2000 10:08:23 +0100 [thread overview]
Message-ID: <0G2M00EBTC1Z6M@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Tue, 17 Oct 2000 14:21:11 PDT." <001017142111.ZM3802@candle.brasslantern.com>
Bart wrote:
> On Oct 17, 3:35pm, E. Jay Berkenbilt wrote:
> >
> > 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.
>
> 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.
There was originally a partial fix that the rest of the line gets read in
and stuck on the end of the history without lexing. I haven't looked at
this for a long time, so it may be at the mercy of various flags which
abort what you're doing. It might be possible to get it working.
--
Peter Stephenson <pws@csr.com> Software Engineer
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
next prev parent reply other threads:[~2000-10-18 9:08 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
2000-10-18 9:08 ` Peter Stephenson [this message]
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=0G2M00EBTC1Z6M@la-la.cambridgesiliconradio.com \
--to=pws@csr.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).