zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: random attribute stuff
Date: Tue, 06 May 2008 08:38:02 -0700	[thread overview]
Message-ID: <080506083802.ZM1323@torch.brasslantern.com> (raw)
In-Reply-To: <200805061510.m46FA71C001035@news01.csr.com>

On May 6,  4:10pm, Peter Stephenson wrote:
}
} > It almost certainly *won't* work except in the most simple cases now that
} > ZLE is doing its own highlighting effects.  People are going to have to
} > decide whether they want that badly enough to use zle_highlight=(none).
} 
} I tried it without any highlighting.

It works for me in xterm if I e.g. assign PS1="$PS1%U" ... in fact for
the most part even the active region highlight doesn't screw it up, you
appear to be doing a good job of turning off only the seuqnces that you
previously turned on.  (I did not try more complicated effects than %U.)

(It's a bit odd that %U persists into the right prompt unless turned off
with PRS1="%u$RPS1" but it has always been that way.)
 
} It ought to be (but might turn out not to be) fairly easy to add a
} "default" element to zle_highlight that causes the given attributes to
} be used as the default set for the command line, which would probably
} work a lot better, and then deprecate any reliance on what the prompt
} happened to produce.

Sounds reasonable to me, but could get ugly if a widget were to change
it on the fly -- do you trap that and reprint the entire buffer, or do
you allow blotches of different attributes as areas are selectively
repainted, or do you make that setting read-only in widgets?


  reply	other threads:[~2008-05-06 15:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06  9:15 Peter Stephenson
2008-05-06 14:34 ` Bart Schaefer
2008-05-06 14:42   ` Peter Stephenson
2008-05-06 14:58     ` Bart Schaefer
2008-05-06 15:10       ` Peter Stephenson
2008-05-06 15:38         ` Bart Schaefer [this message]
2008-05-06 15:48           ` Peter Stephenson
2008-05-06 18:16             ` Peter Stephenson
2008-05-07 15:44               ` Oliver Kiddle
2008-05-07 15:49               ` Oliver Kiddle
2008-05-07 15:55                 ` 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=080506083802.ZM1323@torch.brasslantern.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).