From: David De La Harpe Golden <david@harpegolden.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Presto Ten <presto08@me.com>, Emacs-devel@gnu.org
Subject: Re: Add "lisp/term/screen-256color.el" for GNU Screen's 256 color mode?
Date: Fri, 20 Feb 2009 17:46:53 +0000 [thread overview]
Message-ID: <499EEC8D.5050404@harpegolden.net> (raw)
In-Reply-To: <jwv3ae9p2ny.fsf-monnier+emacs@gnu.org>
Stefan Monnier wrote:
> Having a function terminal-init-screen in file screen-256color.el
> doesn't make sense. The function probably needs to be renamed to
> terminal-init-screen-256color. OTOH the file could probably be named
> just term/screen.el
The matching algo documented in term/README means that in the
TERM=screen-256color case, if there's no screen-256color.el, emacs falls
back to screen.el ?
In that case, having the file called called screen.el and that function
terminal-init-screen makes a lot of sense since the code Trent posted
anyway reuses the bits of term/xterm.el which are intended to do the
right thing for xterm vs. xterm-256color when xterm-256color falls back
to xterm.el
=> So if that terminal-init-screen is used, calling it that and putting
it in term/screen.el is for the best as far as I can see.
next prev parent reply other threads:[~2009-02-20 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 9:12 Add "lisp/term/screen-256color.el" for GNU Screen's 256 color mode? Presto Ten
2009-02-20 15:15 ` Stefan Monnier
2009-02-20 17:46 ` David De La Harpe Golden [this message]
2009-02-20 21:09 ` Stefan Monnier
2009-02-21 14:22 ` David De La Harpe Golden
2009-03-06 19:38 ` presto08
2009-03-07 19:38 ` Chong Yidong
2009-02-20 18:44 ` presto08
2009-02-20 21:10 ` Stefan Monnier
2009-02-20 21:22 ` presto08
-- strict thread matches above, loose matches on Subject: below --
2009-03-07 13:04 Xavier Maillard
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=499EEC8D.5050404@harpegolden.net \
--to=david@harpegolden.net \
--cc=Emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=presto08@me.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 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).