all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Miles Bader <miles.bader@necel.com>
Cc: emacs-devel@gnu.org
Subject: Re: RFC: comint.el - comint-highlight-prompt and unreadable colors
Date: Mon, 26 Mar 2007 19:18:50 -0700	[thread overview]
Message-ID: <200703270218.l2R2IoXK021694@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <buok5x3xyel.fsf@dhapc248.dev.necel.com> (Miles Bader's message of "Tue\, 27 Mar 2007 10\:34\:10 +0900")

Miles Bader <miles.bader@necel.com> writes:

  > Stefan Monnier <monnier@iro.umontreal.ca> writes:
  > > Problem is: in terminal mode, menus are also more difficult to
  > > use :-( I wish PuTTY used a special TERM setting (or alternatively, I wish
  > > the xterm control-sequences included one which can be used to identify the
  > > terminal in use, and maybe even its background color).  Maybe we should
  > > write&submit a patch to X.org (or whoever is maintaining xterm nowadays) for
  > > that, so that we can use it in Emacs-23.
  > 
  > Yeah; someone mentioned that rxvt, while it uses TERM=xterms, defines
  > some extra environment variables.  I just checked, and I see these:
  > 
  >    # black-on-white rxvt (the default)
  >    TERM="xterms"
  >    COLORFGBG="0;15"
  >    COLORTERM="rxvt"
  > 
  >    # white-on-black rxvt (rxvt -fg white -bg black)
  >    TERM="xterms"
  >    COLORFGBG="15;0"
  >    COLORTERM="rxvt"
  > 
  >    # green-on-black rxvt (rxvt -fg green -bg black)
  >    TERM="xterms"
  >    COLORFGBG="10;0"
  >    COLORTERM="rxvt"
  > 
  > Not perfect (it would be better to actually get the terminal's whole
  > colormap in absolute terms) but that seems enough for emacs to do a
  > decent job of setting up the background type at least.
  > 
  > 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

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?

  > and as you say, submit a patch to make xterm define the
  > same variables.

  > [An additional variable giving the whole colormap would be even nicer,
  > e.g.:
  > 
  >    COLORMAP="0:#000000,1:#ff0000,2:#00ff00,..."
  > 
  > Maybe we could try to submit a patch to export that info too...]

Now all the major terminal implementations support 256 colors...
(luckily except rxvt, all implement the xterm color scheme for the
colors 16-256)

  reply	other threads:[~2007-03-27  2:18 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 [this message]
2007-03-27  4:02                               ` Miles Bader
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200703270218.l2R2IoXK021694@oogie-boogie.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=miles.bader@necel.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.