From: Nicolas Semrau <nicolas.semrau@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Kangas <stefan@marxist.se>,
37562@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#37562: 26.2; Obsolete vt-control and vt100-led
Date: Fri, 8 Nov 2019 12:45:10 +0100 [thread overview]
Message-ID: <CAMC+NsTFtrd5OG2j4rXm0PQ2RVHav4Wk2jsKmcxRwYbSzYaG3g@mail.gmail.com> (raw)
In-Reply-To: <83v9rud715.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
> There's no tangible benefit in obsoleting these tiny files.
So files like this will probably stay in the codebase indefinitely?
I am aware that they do not make Emacs "worse", performance-wise. I
just think linting files for those unused stone-age systems is
beneficial at least in the sense of alleviating a certain "museum
piece vibe" of Emacs.
Am Fr., 8. Nov. 2019 um 10:58 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
> > From: Stefan Kangas <stefan@marxist.se>
> > Date: Fri, 8 Nov 2019 01:02:35 +0100
> > Cc: nicolas.semrau@gmail.com, 37562@debbugs.gnu.org,
> > Stefan Monnier <monnier@iro.umontreal.ca>
> >
> > Would it make sense to mark them as obsolete and if anyone complains
> > to create a new ELPA package for them instead? We could even say in
> > NEWS that, in case anyone is still using this, we would appreciate it
> > if they reported back to emacs-devel or somesuch. (I think I've seen
> > that being done once before, so there is some precedent.)
> >
> > My objective in writing this is to figure out a way forward for the
> > original request/suggestion, but I don't feel very strongly about it.
> > However, if we can't find a reasonable way to do this, or if we don't
> > want to, I think we're better off closing this as wontfix.
>
> I prefer the latter. This issue is so minor that we've already
> invested way too much energy in it. There's no tangible benefit in
> obsoleting these tiny files.
>
[-- Attachment #2: Type: text/html, Size: 2199 bytes --]
next prev parent reply other threads:[~2019-11-08 11:45 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 [this message]
2019-11-08 13:41 ` Eli Zaretskii
2022-02-02 18:41 ` Lars Ingebrigtsen
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=CAMC+NsTFtrd5OG2j4rXm0PQ2RVHav4Wk2jsKmcxRwYbSzYaG3g@mail.gmail.com \
--to=nicolas.semrau@gmail.com \
--cc=37562@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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).