From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r116893: Introduce `term-file-aliases', replacing some small lisp/term files
Date: Thu, 27 Mar 2014 22:12:38 -0400 [thread overview]
Message-ID: <jwvppl7nkdw.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <E1WTLcO-0006lp-RH@vcs.savannah.gnu.org> (Glenn Morris's message of "Fri, 28 Mar 2014 01:30:00 +0000")
> +(defvar term-file-aliases
> + '(("apollo" . "vt100")
> + ("vt102" . "vt100")
> + ("vt125" . "vt100")
> + ("vt201" . "vt200")
> + ("vt220" . "vt200")
> + ("vt240" . "vt200")
> + ("vt300" . "vt200")
> + ("vt320" . "vt200")
> + ("vt400" . "vt200")
> + ("vt420" . "vt200")
> + )
We don't strictly need it since we can define functions
terminal-init-apollo, terminal-init-vt102, ...
Stefan
parent reply other threads:[~2014-03-28 2:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1WTLcO-0006lp-RH@vcs.savannah.gnu.org>]
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=jwvppl7nkdw.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).