From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Peter Stephenson <pws@ibmth.df.unipi.it>,
zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: zsh exits suddenly.
Date: Thu, 25 Jun 1998 09:57:52 -0700 [thread overview]
Message-ID: <980625095752.ZM3603@candle.brasslantern.com> (raw)
In-Reply-To: <9806250833.AA27200@ibmth.df.unipi.it>
On Jun 25, 10:33am, Peter Stephenson wrote:
} Subject: Re: zsh exits suddenly.
}
} The proper use of inerrflush() is when lexing the line just input.
} I've found the difference: it's in a case like this:
}
} % print !!:s/foo/bar/<ESC><RET>
} print haha
}
} The current code gives an error message for the substitution (assuming
} of course there was no `foo' in the previous line), but prints `haha'
} anyway. Without the lastc stuff, the `print haha' is discarded along
} with the rest of the previous line.
}
} So the question boils down to: after a history subsitution failure,
} should the rest of the input be discarded, or just the rest of the
} line as at present? (Note parsing failures don't flush the input in
} any case [...]
Aha. I think both substitution errors -and- parsing failures ought to
consume the entire remainder of the input. Consider what happens if
the statement following the error is something destructive like a "rm",
which was e.g. expected to happened in a different directory.
It's also probably a good idea in light of the strange way the results
end up in the history on a parse error.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1998-06-25 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <980623112518.ZM375@candle.brasslantern.com>
1998-06-24 8:51 ` Peter Stephenson
1998-06-24 16:17 ` Bart Schaefer
1998-06-25 8:33 ` Peter Stephenson
1998-06-25 16:57 ` Bart Schaefer [this message]
1998-06-26 10:17 ` PATCH: 3.1.4: flushing input properly Peter Stephenson
1998-06-26 16:54 ` Bart Schaefer
1998-06-26 18:17 ` Zefram
1998-06-27 11:59 ` Peter Stephenson
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=980625095752.ZM3603@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=pws@ibmth.df.unipi.it \
--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).