unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles.bader@necel.com>
To: emacs-devel@gnu.org
Subject: Re: RFC: comint.el - comint-highlight-prompt and unreadable colors
Date: Tue, 27 Mar 2007 13:02:53 +0900	[thread overview]
Message-ID: <buovegnwcya.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: 200703270218.l2R2IoXK021694@oogie-boogie.ics.uci.edu

Dan Nicolaescu <dann@ics.uci.edu> writes:
>   > So I think Emacs could use the above information if it's present, which
>   > will cover rxvt, 
>
> Emacs does use the above information correctly (i.e. it sets the
> default background and the colormap) IFF TERM is set to: xterm,
> xterm-*, rxvt or rxvt-*.
>
> TERM=xterms is equivalent to not having any terminal initialization
> code in lisp/term/*.el

Emacs ought to handle "xterms" too; it's a historical artifact of sorts,
but it used to be very common.

> Where does "xterms" come from? Is is a default setting on some
> systems, or just a user that thought it would be a good idea to set
> TERM to that?

I looked around a bit more, and realized, it's my fault -- it's from my
~/.Xresources file:

    XTerm*termName: xterms

What's really strange is that the real xterm doesn't seem to use that
resource, only rxvt does... so it went unnoticed for ages.

Anyway, I removed that line, and now when I run rxvt, TERM="rxvt", and
Emacs colors are set up properly by default no matter what colors rxvt
is using.

Thanks for the clue that something was funny...

-miles
-- 
Quidquid latine dictum sit, altum viditur.

  reply	other threads:[~2007-03-27  4:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25 10:53 RFC: comint.el - comint-highlight-prompt and unreadable colors Jari Aalto
2007-03-25 13:31 ` Miles Bader
2007-03-25 15:18   ` Jari Aalto
2007-03-25 20:11     ` Robert J. Chassell
2007-03-26  7:26       ` Jari Aalto+mail.emacs
2007-03-25 23:43     ` Miles Bader
2007-03-26  5:12       ` Jari Aalto
2007-03-26  5:44         ` Miles Bader
2007-03-26  7:22           ` Jari Aalto+mail.emacs
2007-03-26 20:59             ` Eli Zaretskii
2007-03-26  7:56           ` Romain Francoise
2007-03-26  9:24             ` Miles Bader
2007-03-26  9:34               ` Jari Aalto+mail.emacs
2007-03-26 10:05                 ` Miles Bader
2007-03-26 10:22                   ` Jari Aalto+mail.emacs
2007-03-26 12:17                     ` Miles Bader
2007-03-26 12:45                       ` tomas
2007-03-26 13:27                         ` Stefan Monnier
2007-03-26 21:08                           ` Eli Zaretskii
2007-03-27  1:34                           ` Miles Bader
2007-03-27  2:18                             ` Dan Nicolaescu
2007-03-27  4:02                               ` Miles Bader [this message]
2007-03-29 14:44                           ` tomas
2007-03-29 16:10                             ` Stefan Monnier
2007-03-30  5:16                               ` tomas
2007-03-26 14:51                       ` Jari Aalto+mail.emacs
2007-03-26 16:51                         ` Miles Bader
2007-03-26 13:28                     ` Robert J. Chassell
2007-03-26 16:24           ` Dan Nicolaescu

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=buovegnwcya.fsf@dhapc248.dev.necel.com \
    --to=miles.bader@necel.com \
    --cc=emacs-devel@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.
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).