From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Change color of 'highlight' indicator in inbox view?
Date: Wed, 09 Sep 2009 07:30:43 -0700 [thread overview]
Message-ID: <1252506333-sup-9244@masanjin.net> (raw)
In-Reply-To: <1252442174-sup-1472@yoom.home.cworth.org>
Reformatted excerpts from Carl Worth's message of 2009-09-08:
> So if I'm understanding that correctly, that's 16 colors available for
> the foreground, but only 8 for the background. That's frustrating.
Yup. Curses is happy to welcome you to 1982!
> Such a limited color selection is almost unimaginable with hardware
> capability today.
FWIW, most terminal emulators allow you to tweak the actual colors that
the curses colors refer to. So you have some flexibility about the
actual colors, just a small palette.
> (I do see references to "xterm-256color"[*] terminal definitions.
> Could sup start depending on things like that? Are there users of sup
> using the Linux console or so, and does that support 256-color escape
> codes?).
I'm not sure. I suspect no, but I would be interested in learning more.
> I should figure out how to make the underline vs. color choice for
> highlighting to be a configuration option in order to propose this as
> a proper patch.
I think the only patch I would accept at this point for tweaking the
highlight would be a new hook.
> Of course, one way is to go away from a curses-based interface. That
> might very well make sense in the future where sup is implemented as a
> protocol and we can easily have multiple clients.
That is one of the goals.
> For me, a graphical client won't be of any interest unless it allows
> full keyboard control exactly as sup does, but if it does that and
> renders text as well as my terminal, I could imagine using it.
I agree completely.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-09-09 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 9:42 Richard Sandilands
2009-09-06 13:07 ` William Morgan
2009-09-08 20:50 ` Carl Worth
2009-09-09 14:30 ` William Morgan [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=1252506333-sup-9244@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox