zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: re-expand the prompt automatically
Date: Mon, 05 Jul 2004 10:26:07 +0100	[thread overview]
Message-ID: <200407050926.i659Q7e3004504@news01.csr.com> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Sun, 04 Jul 2004 14:38:13 PDT." <Pine.LNX.4.60.0407041406560.24553@toltec.zanshin.com>

Bart Schaefer wrote:
> > 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 think I misinterpreted your use of `option'... I presumed you meant
something like `setopt always_redraw_prompt', whereas you presumably
meant something link `zle -P'.  I can certainly see an argument for that
but, as you say, it's all a bit murky.

-- 
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-07-05  9:27 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
2004-07-05  9:26         ` Peter Stephenson [this message]

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=200407050926.i659Q7e3004504@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).