From: Zefram <zefram@dcs.warwick.ac.uk>
To: zsh-workers@math.gatech.edu (Z Shell workers mailing list)
Subject: bug: EOF at a continuation prompt
Date: Sat, 30 Nov 1996 18:11:00 +0000 (GMT) [thread overview]
Message-ID: <12037.199611301811@stone.dcs.warwick.ac.uk> (raw)
% (
subsh> ^D
zsh: parse error near `\n'
>
That bare ">" prompt shouldn't appear. We should go back to the ZLE
prompt. The culprit seems to be in input.c:
/*
* Otherwise, see if we have reached the end of input
* (due to an error, or to reading from a single string).
*/
if (strin || errflag) {
lexstop = 1;
return lastc = ' ';
}
/* As a last resort, get some more input */
if (inputline())
return lastc = ' ';
It looks like the first if() here should be used, but errflag is zero.
Consequently inputline() gets called.
And look what happens if you type at that extra prompt:
> ls
zsh: command not found: s
Huh?
-zefram
reply other threads:[~1996-11-30 18:36 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=12037.199611301811@stone.dcs.warwick.ac.uk \
--to=zefram@dcs.warwick.ac.uk \
--cc=zsh-workers@math.gatech.edu \
/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).