zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: zsh exits after delete-char-or-list and two ^Cs
Date: Tue, 07 Sep 2004 15:08:57 +0100	[thread overview]
Message-ID: <200409071408.i87E8vQO004330@news01.csr.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0409030827210.28049@toltec.zanshin.com>

> On Fri, 3 Sep 2004, Peter Stephenson wrote:
> > Bart Schaefer wrote:
> > >   zle && echo "widgets callable"	# I'm least certain of this
> > >   zle -I && echo "Display invalidated and widgets callable"
> > >   zle -R && echo "Display refreshed and zle active"
> > > 
> > > Is that right?
> > 
> > Yes, noting that testing for `display invalidated' and `display
> > refreshed' doesn't form part of the return status (I think that's what
> > you mean but it's not clear from the output).
> 
> Hmm.  OK, that's not so good, because it breaks "zle -I || ..." in the 
> case where you want to know whether the display was NOT invalidated.
> (Maybe there's never a reason to care about that, but ...)

I don't think there is, in fact, but for the sake of logic it's probably
worth changing.  I've looked at the pattern of usage of zle -I in the
various functions I've got and I never test the return value at all:
either zle wasn't active, or it's been invalidated, and either are good
enough for me.  (I do, however, test [[ -o zle ]] beforehand to avoid
having to load it if it wasn't in use.)

It would require putting the test back to testing for zleactive.  That
means your original example wouldn't work, but as you say that's really
a problem with the documentation for when I feel fit enough to look at
the zle documentation again.

The display is refreshed if and only if zle is active on zle -R, so that
doesn't need changing.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


  reply	other threads:[~2004-09-07 14:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25 17:04 Danek Duvall
2004-08-27  0:22 ` Bart Schaefer
2004-09-01 18:10   ` Peter Stephenson
2004-09-01 19:44     ` Bart Schaefer
2004-09-02  9:19       ` Peter Stephenson
2004-09-02 15:15         ` Bart Schaefer
2004-09-03  9:37           ` Peter Stephenson
2004-09-03 18:59             ` Bart Schaefer
2004-09-07 14:08               ` Peter Stephenson [this message]
2004-09-08 14:23               ` Peter Stephenson
2004-09-01 17:36 ` 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=200409071408.i87E8vQO004330@news01.csr.com \
    --to=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).