zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: zsh exits after delete-char-or-list and two ^Cs
Date: Thu, 2 Sep 2004 08:15:42 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0409020755430.18377@toltec.zanshin.com> (raw)
In-Reply-To: <200409020919.i829J0eC012233@news01.csr.com>

On Thu, 2 Sep 2004, Peter Stephenson wrote:

> It looks like it would be more sensible to have the test for whether a
> zle widget is callable separate from the return status for zle -I.

What about zle -R ?

I think (but haven't applied it yet) that with this patch we have

  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?

This covers all bases, assuming it's harmless to call zle -R even when you 
don't really care whether the display is refreshed.  Unless one might need
to know that the display has been invalidated even when widgets are not
callable?  I'm having a hard time coming up with that.

> However, it's a bit late now.

Well, no, not really -- if in fact "zle" with no arguments does correctly 
mean "widgets callable", then "zle -I" could continue as "zle active".
Perhaps this was all a documentation problem to begin with.

Sorry to nit-pick, but:

> Index: Doc/Zsh/zle.yo
> ===================================================================
> +The returned status is zero if a zle widget can be called immediately.
> +Note this is independent of whether the display has been invalidated.
> +For example, if a completion widget is active a zle widget cannot be used
> +and the status is one even if the display was invalidated; on the other
> +hand, the status may be zero if the display was invalidated by a previous
> +call to `tt(zle -I)'.

Isn't it more accurate to say "the status may be nonzero even if the 
display was invalidated by a previous call"?  With the rest of the patch 
as it stands, the status is never zero when completion widgets are active, 
even when the display was previously invalidated -- but the above seems to 
imply that the status might be zero in that event.


  reply	other threads:[~2004-09-02 15:24 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 [this message]
2004-09-03  9:37           ` Peter Stephenson
2004-09-03 18:59             ` Bart Schaefer
2004-09-07 14:08               ` Peter Stephenson
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=Pine.LNX.4.61.0409020755430.18377@toltec.zanshin.com \
    --to=schaefer@brasslantern.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).