From: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: support for rxvt-unicode in rxvt.el
Date: Wed, 21 Sep 2005 14:02:16 -0700 [thread overview]
Message-ID: <200509212102.j8LL2IKE011172@scanner2.ics.uci.edu> (raw)
In-Reply-To: <742051605092112545d674084@mail.gmail.com> (Emanuele Giaquinta's message of "Wed, 21 Sep 2005 21:54:48 +0200")
Emanuele Giaquinta <emanuele.giaquinta@gmail.com> writes:
> On 9/21/05, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
> > Such key sequences have been added to xterm.el because at some point they've
> > been found to be necessary. Maybe nowadays they're redundant. If they're
> > not necessary for rxvt.el, better not add them. Removing them from xterm.el
> > is more delicate since we'd need to know for sure that they're
> > always unnecessary, otherwise we might (re)introduce bugs.
>
> Fine, follows an updated patch.
> BTW I've noticed Dan has changed the definitions of white and
> brightblack in rxvt.el; Dan, what is the reason for this change? The
> previous ones were the definitions of rxvt.
The new definitions correspond to the colors emitted by rxvt.
(You can take a screen dump and check if you want).
next prev parent reply other threads:[~2005-09-21 21:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 13:24 support for rxvt-unicode in rxvt.el Emanuele Giaquinta
2005-09-21 13:52 ` Stefan Monnier
2005-09-21 14:03 ` Emanuele Giaquinta
2005-09-21 14:26 ` Dan Nicolaescu
2005-09-21 14:35 ` Emanuele Giaquinta
2005-09-21 14:50 ` Dan Nicolaescu
2005-09-21 14:58 ` Emanuele Giaquinta
2005-09-21 16:30 ` Dan Nicolaescu
2005-09-21 16:29 ` Dan Nicolaescu
2005-09-21 16:43 ` Emanuele Giaquinta
2005-09-21 17:25 ` Stefan Monnier
2005-09-21 19:54 ` Emanuele Giaquinta
2005-09-21 21:02 ` Dan Nicolaescu [this message]
2005-09-22 8:01 ` Emanuele Giaquinta
2005-09-24 23:28 ` Dan Nicolaescu
2005-09-25 0:23 ` Emanuele Giaquinta
2005-09-21 21:38 ` Andreas Schwab
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=200509212102.j8LL2IKE011172@scanner2.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).