From: Wayne Davison <wayned@users.sourceforge.net>
To: Peter Stephenson <pws@csr.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: zle history entry paranoia
Date: Mon, 24 Jun 2002 13:28:04 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0206241318100.9313-100000@miketv.blorf.net> (raw)
In-Reply-To: <2323.1024939930@csr.com>
On Mon, 24 Jun 2002, Peter Stephenson wrote:
> This makes it safer by checking the return values of some
> quietgethist's in zle_hist.c.
FYI: I gave the patch look, and it looks good to me. The only "hmm"
spot was in the doisearch function where a couple calls got reordered
a bit, but a quick glance at the code satisfied me that things were OK.
Seems like a very reasonable change.
..wayne..
prev parent reply other threads:[~2002-06-24 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 17:32 Peter Stephenson
2002-06-24 20:28 ` Wayne Davison [this message]
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=Pine.LNX.4.44.0206241318100.9313-100000@miketv.blorf.net \
--to=wayned@users.sourceforge.net \
--cc=pws@csr.com \
--cc=zsh-workers@sunsite.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).