Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marka@pobox.com (Mark Alexander)
Subject: [sup-talk] Strange random changing of default colors
Date: Wed, 20 May 2009 07:55:28 -0700	[thread overview]
Message-ID: <a412e2a70905200755n58df4ed2k77b9a1926d876ee@mail.gmail.com> (raw)

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.  When
I start it, things are fine for a few minutes, and the default
colors (for things like the unused portion of the display
or quoted text) are fine.  Then after a few minutes,
the default colors will get changed to yellow-on-black,
or black-on-red, or some other strange thing.  I haven't
been able to track down exactly what causes this.
Sometimes it happens when going through my inbox;
sometimes from doing a '/' to search for a string.

The only thing I can say is that the new default colors
seem to have been picked from some line that was
being displayed by sup.  For example, a few times
when an "unreceived message" line was being displayed
in a thread, and I moved the highlight over that line,
the default colors got changed to the colors of that
line (black on red in this case).

I've seen this on both Fedora Core 4 with xterm,
and OpenSUSE 10.2 with konsole.  So it's possible
it's a problem with older versions of ncurses.
I'll try this on Ubuntu 8.10 at some point soon.

Has anybody else noticed this?


             reply	other threads:[~2009-05-20 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20 14:55 Mark Alexander [this message]
     [not found] ` <1242840017-sup-6420@cabinet>
2009-05-20 18:04   ` Mark Alexander
2009-05-20 18:52 ` William Morgan
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=a412e2a70905200755n58df4ed2k77b9a1926d876ee@mail.gmail.com \
    --to=marka@pobox.com \
    /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