zsh-workers
 help / color / mirror / code / Atom feed
From: Anthony Heading <aheading@jpmorgan.com>
To: schaefer@brasslantern.com (Bart Schaefer)
Cc: zsh-workers@math.gatech.edu
Subject: Re: zsh-3.1.2-zefram3
Date: Wed, 21 Jan 1998 18:37:12 +0000 (GMT)	[thread overview]
Message-ID: <199801211837.SAA07825@gmp-etpres1.uk.jpmorgan.com> (raw)
In-Reply-To: <980118093836.ZM5175@candle.brasslantern.com> from Bart Schaefer at "Jan 18, 98 09:38:36 am"

Bart wrote:
> This is true, but seems clumsy especially because the EOF char is normally
> overloaded as delete-char-or-list.  You'd be forced to write a user-defined
> widget that implemented `delete-char-or-list-or-eof' to make it work right.

Indeed.

> On the other hand, I don't believe that vared *should* behave the way that
> typing text into `cat` would.  Vared is not a streaming editor; I expect
> it to behave like an editor that controls my terminal, not like a process
> blindly reading from standard input.

OK. I suppose I was thinking that vared could easily be a streaming editor,
and read standard input slightly less blindly.

> How exactly does this change the behavior, again?  EOF on any empty line
> is EOF, even in a multiline edit?  Yes, I object to that.  I want EOF to
> be EOF when typed on an empty line at a PS1 prompt, and nowhere else.

Fair.  But I want EOF to be EOF also in my vared-based `cat' emulator.

So at most, then, this should be an option for vared, and not a default.

I shall revamp my patch to be less intrusive, and not change any of the
current behaviour.

Cheers

A


  parent reply	other threads:[~1998-01-21 18:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-12 11:27 zsh-3.1.2-zefram3 Andrew Main
1998-01-13  9:29 ` zsh-3.1.2-zefram3 on Solaris Andrei Tcherepanov
1998-01-13 11:46   ` Andrew Main
1998-01-18 15:14 ` zsh-3.1.2-zefram3 Anthony Heading
1998-01-18 17:38   ` zsh-3.1.2-zefram3 Bart Schaefer
1998-01-19  8:58     ` zsh-3.1.2-zefram3 Peter Stephenson
1998-01-21 18:37     ` Anthony Heading [this message]
1998-01-13 11:44 zsh-3.1.2-zefram3 Bruce Stephens
1998-01-13 12:19 ` zsh-3.1.2-zefram3 Andrew Main
1998-01-13 12:49   ` zsh-3.1.2-zefram3 Bruce Stephens
1998-01-13 13:36   ` zsh-3.1.2-zefram3 Peter Stephenson
1998-01-13 15:04     ` zsh-3.1.2-zefram3 Bruce Stephens
1998-01-13 11:56 zsh-3.1.2-zefram3 Sven Wischnowsky
1998-01-13 11:59 zsh-3.1.2-zefram3 Bruce Stephens
1998-01-13 12:24 ` zsh-3.1.2-zefram3 Andrew Main
1998-01-13 12:44   ` zsh-3.1.2-zefram3 Bruce Stephens
1998-01-20  0:46 zsh-3.1.2-zefram3 Gene Cohler

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=199801211837.SAA07825@gmp-etpres1.uk.jpmorgan.com \
    --to=aheading@jpmorgan.com \
    --cc=schaefer@brasslantern.com \
    --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).