zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Peter Stephenson <pws@ibmth.df.unipi.it>
Cc: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: zsh exits suddenly.
Date: Wed, 24 Jun 1998 09:17:12 -0700	[thread overview]
Message-ID: <980624091713.ZM4823@candle.brasslantern.com> (raw)
In-Reply-To: <9806240851.AA45920@ibmth.df.unipi.it>

On Jun 24, 10:51am, Peter Stephenson wrote:
} Subject: Re: zsh exits suddenly.
}
} I can't be absolutely sure if all that lastc stuff is really needed.
} It means, of course, that if there is more than one line in the
} buffer, only the current one is flushed.  Is this the right behaviour?

This isn't changed by your patch, right?  It was the behavior all along?

I think the intent is to prevent accept-line from executing a partial
line following a tty interrupt.  That probably ought to apply to multi-
line buffers as well.  The guideline should probably be, what does ZLE
do to a multiline buffer when send-break is executed?  The SIGINT handler
ought to do the same thing.  (In fact, why doesn't it call sendbreak()
when ZLE is active?)

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1998-06-24 16:37 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 [this message]
1998-06-25  8:33     ` Peter Stephenson
1998-06-25 16:57       ` Bart Schaefer
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=980624091713.ZM4823@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).