unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles.bader@necel.com>
To: Jari Aalto <jari.aalto@cante.net>
Cc: emacs-devel@gnu.org
Subject: Re: RFC: comint.el - comint-highlight-prompt and unreadable colors
Date: Mon, 26 Mar 2007 18:24:11 +0900	[thread overview]
Message-ID: <buo4po8we6c.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <87wt14a158.fsf@pacem.orebokech.com> (Romain Francoise's message of "Mon\, 26 Mar 2007 09\:56\:35 +0200")

Romain Francoise <romain@orebokech.com> writes:
>> On windows, I don't know, but it's probably a similar problem.
>
> I don't think it's related to TERM, PuTTY sets it to "xterm".

Actually that's probably the _reason_ the problem arises:  If TERM =
"xterm", then Emacs assumes a light background (it's a hack, but it was
decided when we discussed this a long time ago that light-background
xterm instances were more common than dark-background instances,
especially for newbies).

> Actually, the `frame-set-background-mode' function suggests that the
> logic is a bit more convoluted...

No doubt.  But it seems pretty likely this is the problem Jari is
seeing, and the solution is obvious:  he should customize
`frame-background-mode' to match his environment.

-Miles

-- 
(\(\
(^.^)
(")")
*This is the cute bunny virus, please copy this into your sig so it can spread.

  reply	other threads:[~2007-03-26  9:24 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 [this message]
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
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=buo4po8we6c.fsf@dhapc248.dev.necel.com \
    --to=miles.bader@necel.com \
    --cc=emacs-devel@gnu.org \
    --cc=jari.aalto@cante.net \
    --cc=miles@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).