zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: zle recursive editing.
Date: Mon, 01 Jul 2002 10:52:09 +0100	[thread overview]
Message-ID: <23948.1025517129@csr.com> (raw)
In-Reply-To: ""Bart Schaefer""'s message of "Sun, 30 Jun 2002 21:19:25 -0000." <1020630211925.ZM15781@candle.brasslantern.com>

"Bart Schaefer" wrote:
> On Jun 30,  9:53pm, Peter Stephenson wrote:
> } Subject: PATCH: zle recursive editing.
> }
> } This simple patch (only the trivial function recursiveedit is new, the
> } rest is just rearrangement, mostly to move the core functions from
> } zlemain to a new function zlecore) has a lot of mileage.
> 
> Cool.  Now if there were some way to get the various "minibuffer" commands
> like execute-named-command to use recursive editing with a separate keymap,
> we could really do some interesting stuff.

Another thing I thought of which might be useful is a way to protect
areas of the display, so for example if you are using a widget like
select-list you can't move off the list until you accept something or
break.  I think you could do something like this without too much
difficulty by using a special parameter like $PREDISPLAY (maybe also
$POSTDISPLAY, since this gives you more control than zle -M), which would
insert the given lines before (or after) $BUFFER.  This could probably
be done within zle_refresh (and zle_parameter, of course).  It would
probably have to be line-orientated to avoid weird interactions with the
normal buffer, although maybe even that restriction is avoidable.

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


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


  reply	other threads:[~2002-07-01  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-30 20:53 Peter Stephenson
2002-06-30 21:19 ` Bart Schaefer
2002-07-01  9:52   ` Peter Stephenson [this message]
2002-07-01 11:23     ` PATCH: $PREDISPLAY/$POSTDISPLAY Peter Stephenson
2002-07-04  7:57       ` Sven Wischnowsky
2002-07-04  9:57         ` 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=23948.1025517129@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).