From: Steve Revilak <steve@srevilak.net>
To: help-gnu-emacs@gnu.org
Subject: Re: e23 inverse video on mode line and nowhere else
Date: Thu, 14 Jan 2010 23:13:02 -0500 [thread overview]
Message-ID: <20100115041302.GB428@srevilak.net> (raw)
In-Reply-To: <201001142304.o0EN4xZM016949@f7.net>
[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]
>> When I run emacs in terminals, the mode line is always inverse video
>> but the rest is normal.
karl> Thanks for replying, but this is not even remotely true for me
karl> in e23 (it used to be that way, for sure, for many many years).
karl> Now, I start emacs with emacs-23.1 --no-site --no-init in an
karl> xterm, and immediately observe the *scratch* buffer name is in
karl> bold. (Haven't tried tty-suppress-bold-inverse-default-colors
karl> yet, but anyway, that's not so critical.)
I had a bit of a surprise when I first tried Emacs-23. It's only
slightly related to Karl's issue, but I'll mention it anyway.
The first time I tried Emacs-23, I lost reverse video in the mode
line. Talk about disorienting :)
After some trial and error, I discovered the cause. I'd used M-x
customize-face to customize the default face. The customized default
face worked well for a windowed emacs, but not so well for "emacs
-nw". Unfortunately, I don't remember the precise customization, and
the bufferfly has long flipped those bits on my hard drive.
Karl was using --no-init-file --no-site-file, so face customizations
probably have nothing to do with it.
timx> Three possible solutions.
timx>
timx> 1. M-x customize-face will allow you to set the attributes of
timx> various faces.
timx> 3. Turn off global font lock mode. This will result in most
timx> faces just having the 'default' attributes.
Turning off font-lock removes much of the decoration, but seems to
have little effect on compile mode. M-x customize-face might be the
most effective way to de-ornament compile mode.
Steve
[-- Attachment #2: Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2010-01-15 4:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100115004221.598A8AF600@mxperim7.sea5.speakeasy.net>
2010-01-14 23:04 ` e23 inverse video on mode line and nowhere else Karl Berry
2010-01-15 4:13 ` Steve Revilak [this message]
2010-01-15 20:23 ` Leo
2010-02-01 2:04 Karl Berry
[not found] <mailman.1436.1263510311.18930.help-gnu-emacs@gnu.org>
2010-01-15 0:32 ` Tim X
2010-01-15 8:21 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2010-01-13 1:42 Karl Berry
2010-01-13 8:31 ` Leo
2010-01-16 22:35 ` Juri Linkov
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=20100115041302.GB428@srevilak.net \
--to=steve@srevilak.net \
--cc=help-gnu-emacs@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).