zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@berkom.de>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: $PREDISPLAY/$POSTDISPLAY
Date: Thu, 4 Jul 2002 09:57:09 +0200	[thread overview]
Message-ID: <15651.65493.979771.882185@wischnow.berkom.de> (raw)
In-Reply-To: <29128.1025522627@csr.com>


Peter Stephenson wrote:

> ...
> 
> Note the way these parameters survive across invocations of zle.  This
> was simply because it was the most natural way of writing it.  We can
> make zleread() reinitialise them if it seems preferable.

I can see that it's more powerful, but it's really rather irritating,
isn't it? Especially since you can't make them go away from the
(normal) command line. Although with well-behaved widgets...

> Hmm, it would be nice to get bits of these optionally in inverse video.
> In fact, it would be nice to get a lot of other stuff such as the region
> between point and mark in inverse video.

In any kind of mode/colour. It could also be nice if we could restrict
the allowed movement-range in recursive edits (kind of like
narrow-to-region in emacs). And then allow to display more than two
extra strings at any place (I don't have an example in mind, though).

Ultimately, this could get us to enable highlighting of command lines,
as requested several times already. But that's a whole lot more
complicated, obviously.

But it's a nice patch, Peter.


Bye
  Sven

-- 
Sven Wischnowsky                          wischnow@berkom.de


  reply	other threads:[~2002-07-04  7:56 UTC|newest]

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