zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: re-expand the prompt automatically
Date: Sun, 4 Jul 2004 14:38:13 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.60.0407041406560.24553@toltec.zanshin.com> (raw)
In-Reply-To: <20040704171756.0537685BC@pwstephenson.fsnet.co.uk>

On Sun, 4 Jul 2004, Peter Stephenson wrote:

> Bart Schaefer wrote:
> > (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.  [...] zle reset-prompt reexpands the prompt on the 
> current line.

Aha.  I hadn't caught that distinction.

> > 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?

In part this suggestion came from my misinterpretation of reset-prompt (by
the way, the ChangeLog calls it "prompt-reset".)  However:

> Are you suggesting it be tied to zle -R or zle redisplay or both?

Neither ...  Put to it, I don't think "redisplay" should have been a 
built-in widget either, except that for historic reasons it had to be.  
I'm suggesting that built-in widgets should always act on the editor 
buffer (on either the contents or the position of the mark or the cursor) 
whereas zle options -- or special commands like compadd -- should act on 
the editing engine itself (widgets, keymaps, prompts and displays).

My criteria would best be described by the question, "Would it ever make 
sense to use any of the zle -A, -C, -D, or -N options to supercede or 
remove this action?"  If the answer is yes, it should be a widget; if no, 
then either a zle option or a separate command.

I recognize that the line is pretty fuzzy, and now I see that reset-prompt 
is a lot deeper in the fuzz than I originally thought.


  reply	other threads:[~2004-07-04 21:38 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
2004-07-04 21:38       ` Bart Schaefer [this message]
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=Pine.LNX.4.60.0407041406560.24553@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).