unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jari.aalto@cante.net (Jari Aalto+mail.emacs)
To: emacs-devel@gnu.org
Subject: Re: RFC: comint.el - comint-highlight-prompt and unreadable colors
Date: Mon, 26 Mar 2007 12:22:44 +0200	[thread overview]
Message-ID: <lkhk5mob.fsf@blue.sea.net> (raw)
In-Reply-To: buo3b3sz5et.fsf@dhapc248.dev.necel.com

* Mon 2007-03-26 Miles Bader <miles.bader AT necel.com> gmane.emacs.devel
* Message-Id: buo3b3sz5et.fsf AT dhapc248.dev.necel.com
> jari.aalto@cante.net (Jari Aalto+mail.emacs) writes:

>> ...general
>> problem, nothing special to my environment. The problem also happens
>> if user changes the background of rxvt (see previous pictures) at
>> least under Cygwin X11.
>
> No, you are confused.  You clearly haven't read my replies very
> carefully.

Was it "... should customize `frame-background-mode' to match his
environment."

Now I'm confused. 

Should this problem be left to every putty (or dark background term)
user? I understood that the the code doesn't get enough information to
decide the correct dark/light environment in presented cases. So it
might guesses wrong, and the results are pretty bad with the select
default color.

>> Would not default value 'bold, instead of cyan, work better?
>
> No.

Do you have in use cases where 'bold would not work?

Jari

  reply	other threads:[~2007-03-26 10:22 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 [this message]
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=lkhk5mob.fsf@blue.sea.net \
    --to=jari.aalto@cante.net \
    --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).