From: "Matt Wozniski" <godlygeek@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: isearch match highlighting
Date: Tue, 29 Apr 2008 16:12:44 -0400 [thread overview]
Message-ID: <17393e3e0804291312u2ee2f3fcnfb274e295bfc7049@mail.gmail.com> (raw)
In-Reply-To: <20080429181022.12809d23@news01>
On Tue, Apr 29, 2008 at 1:10 PM, Peter Stephenson <pws@csr.com> wrote:
> On Mon, 28 Apr 2008 10:20:01 +0100
> Peter Stephenson <pws@csr.com> wrote:
> > On Sun, 27 Apr 2008 21:49:01 -0400
> > "Matt Wozniski" <godlygeek@gmail.com> wrote:
> > > Yep, works now - and looks very nice, though I wonder if we could set
> > > it up in a way that would let us change the fg or bg color of the
> > > text, rather than just reverse/standout/underline?
> >
> > I should get around to that before long. I don't think it should be too
> > hard. I'd like to use standard termcap AF/AB codes for this instead of the
> > hacked-in (surprise!) colors we currently use in completion, but it doesn't
> > seem to be that easy to set defaults etc. that way. Maybe Geoff knows
> > about this.
>
> This seems now to be Not Necessarily Completely Broken (TM).
Seems to work quite well to me!
> I've just remembered I haven't documented the fact that only colours 0 to
> 255 are allowed internally. I can't be bothered to remake the patch, so
> I'll alter that before committing. The numbers of supported colours
> reported by a few terminals I tried are:
>
> xterm: 8
> rxvt-unicode: 88
> konsole: 8
> gnome-terminal: 8
> Linux console: 8
>
> so mostly just the ANSI set. I did try the extended colours on
> rxvt-unicode and they seemed to work. I have a vague feeling I saw
> a terminal claim to support 256.
xterm-256color: 256
screen-256color: 256
Both xterm and screen can be compiled with 256 color support.
Extended colors seem to work fine in them.
~Matt
PS: Found a typo in the man page while playing with this:
Index: Doc/Zsh/zle.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/zle.yo,v
retrieving revision 1.65
diff -r1.65 zle.yo
2053c2053
< by the array parameter tt(zsh_highlight), if it has been set by the user.
---
> by the array parameter tt(zle_highlight), if it has been set by the user.
next prev parent reply other threads:[~2008-04-29 20:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 22:48 Peter Stephenson
2008-04-27 0:27 ` Matt Wozniski
2008-04-27 16:48 ` Bart Schaefer
2008-04-27 19:57 ` Peter Stephenson
2008-04-28 1:49 ` Matt Wozniski
2008-04-28 9:20 ` Peter Stephenson
2008-04-28 10:50 ` Matt Wozniski
2008-04-28 11:02 ` Peter Stephenson
2008-04-29 17:10 ` Peter Stephenson
2008-04-29 20:12 ` Matt Wozniski [this message]
2008-04-29 20:21 ` Matt Wozniski
2008-05-01 10:37 ` Peter Stephenson
2008-05-02 10:49 ` Nikolai Weibull
2008-05-02 11:14 ` 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=17393e3e0804291312u2ee2f3fcnfb274e295bfc7049@mail.gmail.com \
--to=godlygeek@gmail.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).