From: Stefan Monnier <monnier@iro.umontreal.ca>
To: tomas@tuxteam.de
Cc: Miles Bader <miles.bader@necel.com>, emacs-devel@gnu.org
Subject: Re: RFC: comint.el - comint-highlight-prompt and unreadable colors
Date: Thu, 29 Mar 2007 12:10:35 -0400 [thread overview]
Message-ID: <jwvr6r8jakh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20070329144412.GB9814@www.trapp.net> (tomas@tuxteam.de's message of "Thu\, 29 Mar 2007 14\:44\:12 +0000")
> That's true. So the most elegant way around seems to be Miles' env
> variables...
Are they properly propagated by things like `ssh'?
I'd think a terminal command (i.e. escape sequence) which returns the term's
identification would be even better.
Stefan
next prev parent reply other threads:[~2007-03-29 16:10 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
2007-03-29 14:44 ` tomas
2007-03-29 16:10 ` Stefan Monnier [this message]
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=jwvr6r8jakh.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=miles.bader@necel.com \
--cc=tomas@tuxteam.de \
/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).