From: Stefan Kangas <stefan@marxist.se>
To: emacs-devel@gnu.org
Subject: Relevance of `baud-rate' in the 2020s?
Date: Thu, 22 Oct 2020 14:11:40 -0700 [thread overview]
Message-ID: <CADwFkmn1irDPj2D2fA77yhfWOa1jRZoDj-Y3B8aL_8NJXqU4RA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
So there is this nifty variable called `baud-rate'. It can be used to
enable some special display hacks if you are on a connection slower than
2400 baud. It enables you, I guess, to run Emacs 27.1 on that spanking
new 1987 modem that you have just been dying to get your hands on.
Yet there has been a marked lack of interest in it. :-(
I wasn't able to find any discussion about it on emacs-devel since 2005,
except for an honorable mention when Alan Mackenzie said in 2015 that
the parts in isearch.el that use it are "probably obsolete".
More seriously, is `baud-rate' still relevant in the next decade?
Should we make it obsolete in Emacs 28.1?
PS. To stir up some additional feelings, I've attached a patch that
would remove the "probably obsolete" parts from isearch.el.
[-- Attachment #2: baud-rate-vs-isearch.el --]
[-- Type: application/emacs-lisp, Size: 6559 bytes --]
next reply other threads:[~2020-10-22 21:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 21:11 Stefan Kangas [this message]
2020-10-23 3:45 ` Relevance of `baud-rate' in the 2020s? Richard Stallman
2020-10-23 6:43 ` Eli Zaretskii
2020-10-23 10:21 ` Stefan Kangas
2020-10-23 11:05 ` Eli Zaretskii
2020-10-23 15:09 ` Stefan Monnier
2020-10-23 17:59 ` Eli Zaretskii
2020-10-23 18:32 ` Stefan Monnier
2020-10-23 19:30 ` Eli Zaretskii
2020-10-23 20:44 ` Stefan Monnier
2020-10-23 20:55 ` Stefan Kangas
2020-10-24 8:21 ` Alfred M. Szmidt
2020-10-24 8:57 ` Andreas Schwab
2020-10-24 9:13 ` tomas
2020-10-23 9:02 ` Jean Louis
2020-10-23 10:25 ` Alfred M. Szmidt
-- strict thread matches above, loose matches on Subject: below --
2020-10-26 13:01 Pedro Andres Aranda Gutierrez
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=CADwFkmn1irDPj2D2fA77yhfWOa1jRZoDj-Y3B8aL_8NJXqU4RA@mail.gmail.com \
--to=stefan@marxist.se \
--cc=emacs-devel@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).