From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Strange random changing of default colors
Date: Wed, 20 May 2009 11:52:04 -0700 [thread overview]
Message-ID: <1242845310-sup-6904@entry> (raw)
In-Reply-To: <a412e2a70905200755n58df4ed2k77b9a1926d876ee@mail.gmail.com>
Reformatted excerpts from Mark Alexander's message of 2009-05-20:
> For while now I've been running off of the next branch, and I've been
> noticing strange and hard-to-reproduce problems with sup changing the
> default colors.
I've fixed this in master and next. The problem was that Curses limits
you to a set number of color pairs, and I had thought that limit was 16
(the Ruby bindings don't seem to expose it), and so if you used Sup for
long enough you would eventually run out of colors and it would
helpfully replace old color definitions with new ones for you. :)
But rumors suggest that the limit is more like 64, except in archaic
cases, so I've hard-coded that instead of 16, and experimentally it
seems fine to me (even running through screen).
Let me know if you experience more color weirdness, especially on
archaic systems like Mac OS and Windows.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-05-20 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 14:55 Mark Alexander
[not found] ` <1242840017-sup-6420@cabinet>
2009-05-20 18:04 ` Mark Alexander
2009-05-20 18:52 ` William Morgan [this message]
2009-05-21 16:33 ` Mark Alexander
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=1242845310-sup-6904@entry \
--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