From: marka@pobox.com (Mark Alexander)
Subject: [sup-talk] Patch for using default colors
Date: Sat, 21 Mar 2009 05:57:33 -0700 [thread overview]
Message-ID: <a412e2a70903210557g7587c6fh62b2afb6e4731e9a@mail.gmail.com> (raw)
I noticed that sup wasn't using my terminal's
default colors when displaying the text of
a message. Instead of the expected black on
light-yellow (my defaults), it was using white on black.
I also see a message in the mailing list archives
from Jan 29 titled "When using 'default' in colors.yaml
or colormap.rb, sup throws an exception" that seems
to describe the same problem.
I have attached a patch that works for me, and might
be a workaround for the other problem as well.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: defaultcolors.patch
Type: text/x-patch
Size: 281 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090321/3756fefe/attachment.bin>
next reply other threads:[~2009-03-21 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 12:57 Mark Alexander [this message]
2009-03-23 15:12 ` William Morgan
2009-03-23 15:25 ` William Morgan
2009-03-23 16:34 ` Mark Alexander
2009-03-25 16:02 ` William Morgan
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=a412e2a70903210557g7587c6fh62b2afb6e4731e9a@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