From: Dan Nicolaescu <dann@ics.uci.edu>
To: Jari Aalto <jari.aalto@cante.net>
Cc: 2501@emacsbugs.donarmstrong.com
Subject: bug#2501: 22.2.1: terminal mrxvt white - fonts are unreadable
Date: Fri, 27 Feb 2009 12:14:18 -0800 (PST) [thread overview]
Message-ID: <200902272014.n1RKEIC9020508@rodan.ics.uci.edu> (raw)
In-Reply-To: <87prh3ps2x.fsf_-_@jondo.cante.net> (Jari Aalto's message of "Fri, 27 Feb 2009 22:01:26 +0200")
Jari Aalto <jari.aalto@cante.net> writes:
> Dan Nicolaescu <dann@ics.uci.edu> writes:
> > > On a white mrxt black on white terminal[1], the font-lock colors are
> > > unreadable. See attached picture.
> > >
> > > $ tput colors
> > > 8
> > >
> > > [1] Debian; mrxvt 0.5.3-2 terminal
> > > http://packages.debian.org/mrxvt
> >
> > It appears that emacs thinks that you have dark background. What did
> > you set TERM to?
>
> I started mrxvt from xterm:
>
> $ xterm
> $ echo $TERM
> xterm
> $ mrxvt &
>
> mrxvt$ echo $TERM
> rxvt
> <terminal is open in black on white>
It works just fine for me on Fedora 10, with emacs CVS HEAD, emacs-22.3
on either rxvt and mrxvt.
> > This looks like it is an rxvt derivative, so the value of the COLORFGBG
> > environment variable should help emacs realize what is the default
> > background.
>
> mrxvt$ COLORFGBG=1 emacs -Q -nw
> => Same color results as in previously attached picture
Try setting COLORFGBG to: 0;default
next prev parent reply other threads:[~2009-02-27 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 17:25 bug#2501: 22.2.1: terminal mrxvt white - font's are unreadable Jari Aalto
2009-02-27 18:22 ` Dan Nicolaescu
2009-02-27 20:01 ` bug#2501: 22.2.1: terminal mrxvt white - fonts " Jari Aalto
2009-02-27 20:14 ` Dan Nicolaescu [this message]
2009-02-27 22:03 ` Jari Aalto
2016-01-14 4:58 ` Andrew Hyatt
2016-01-14 16:02 ` Eli Zaretskii
2016-01-16 4:17 ` Andrew Hyatt
2009-02-27 20:09 ` bug#2501: 22.2.1: terminal mrxvt white - font's " Jari Aalto
2022-02-13 10:09 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200902272014.n1RKEIC9020508@rodan.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=2501@emacsbugs.donarmstrong.com \
--cc=jari.aalto@cante.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).