From: Lars Ingebrigtsen <larsi@gnus.org>
To: Nicolas Semrau <nicolas.semrau@gmail.com>
Cc: 37562@debbugs.gnu.org
Subject: bug#37562: 26.2; Obsolete vt-control and vt100-led
Date: Wed, 02 Feb 2022 19:41:58 +0100 [thread overview]
Message-ID: <87y22tp0uh.fsf@gnus.org> (raw)
In-Reply-To: <CAMC+NsRfB0D8mXUZJXLto=1kjx0i+=46m7-L=ondvThTZV1uuw@mail.gmail.com> (Nicolas Semrau's message of "Mon, 30 Sep 2019 18:49:56 +0200")
Nicolas Semrau <nicolas.semrau@gmail.com> writes:
> Five years ago, Stefan Monnier asked if vt100-led.el and vt-control.el
> could be obsoleted.[1] Since there was no objection at the time (and
> the hardware certainly not gaining in popularity since then), I propose
> to go through with declaring /lisp/vt-control.el and /lisp/vt100-led.el
> obsolete.
>
> [1] https://lists.gnu.org/archive/html/emacs-devel/2014-05/msg00169.html
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
I've now moved them to lisp/obsolete in Emacs 29. If it turns out that
they're useful (i.e., we get complaints from people using term/vtXXX),
then we'll reconsider, but it seems unlikely.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-02-02 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 16:49 bug#37562: 26.2; Obsolete vt-control and vt100-led Nicolas Semrau
2019-09-30 18:27 ` Eli Zaretskii
2019-11-07 4:19 ` Stefan Kangas
2019-11-07 14:27 ` Eli Zaretskii
2019-11-08 0:02 ` Stefan Kangas
2019-11-08 9:57 ` Eli Zaretskii
2019-11-08 11:45 ` Nicolas Semrau
2019-11-08 13:41 ` Eli Zaretskii
2022-02-02 18:41 ` Lars Ingebrigtsen [this message]
2022-02-03 1:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 19:13 ` Lars Ingebrigtsen
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=87y22tp0uh.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37562@debbugs.gnu.org \
--cc=nicolas.semrau@gmail.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).