zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: re-expand the prompt automatically
Date: Sun, 04 Jul 2004 18:17:55 +0100	[thread overview]
Message-ID: <20040704171756.0537685BC@pwstephenson.fsnet.co.uk> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Fri, 02 Jul 2004 14:06:21 PDT." <Pine.LNX.4.60.0407021402260.22788@toltec.zanshin.com>

Bart Schaefer wrote:
> On Fri, 2 Jul 2004, Peter Stephenson wrote:
> 
> > Here's the tweak I just proposed to Wayne's patch
> 
> So does this mean "zle reset-prompt" goes away again?  Or does it serve
> a different purpose?

Neither, really, because you still need some way of reexpanding the
prompt when you don't get an asynchronous event.  So it serves the
purpose it always did.

> (It would seem that, with this patch, "zle -I" can be used instead of 
> reset-prompt.

That's not quite true.  zle -I invalidates the display, redrawing the
prompt below.  So at the minimum you get a new line, whether or not the
prompt changed.  zle reset-prompt reexpands the prompt on the current
line.  This is much less intrusive.

> Further, it seems odd to make reset-prompt a built-in 
> widget rather than a zle option.)

I don't understand that.  How would the option know when to reexpand the
prompt?  Are you suggesting it be tied to zle -R or zle redisplay or
both?  (Probably the latter since the former is supposed just to make
the changes requested by widgets explicit rather than refresh the
display.)  Why is that more natural?

-- 
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Work: pws@csr.com
Web: http://www.pwstephenson.fsnet.co.uk


  reply	other threads:[~2004-07-04 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040701164446.GA22234@blorf.net>
2004-07-02 15:23 ` Peter Stephenson
2004-07-02 21:06   ` Bart Schaefer
2004-07-04 17:17     ` Peter Stephenson [this message]
2004-07-04 21:38       ` Bart Schaefer
2004-07-05  9:26         ` 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=20040704171756.0537685BC@pwstephenson.fsnet.co.uk \
    --to=pws@pwstephenson.fsnet.co.uk \
    --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).