all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org
Subject: Re: Relevance of `baud-rate' in the 2020s?
Date: Fri, 23 Oct 2020 14:05:46 +0300	[thread overview]
Message-ID: <83ft65jj79.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkAWdbDyU2AAL5Sd1PDtj3RdtL1zoYc7uFAjTMNJCfG8A@mail.gmail.com> (message from Stefan Kangas on Fri, 23 Oct 2020 10:21:30 +0000)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 23 Oct 2020 10:21:30 +0000
> Cc: emacs-devel@gnu.org
> 
> > If "baud-rate" is what bothers you, we can augment the name or
> > documentation to explain when this is useful and why.
> 
> It could be useful, to avoid that others are left wondering like me.
> OTOH, anyone can now search the emacs-devel archives and find your
> explanation.

Perhaps to prevent any future confusion, we could make the slow
isearch mode dependent on something other than baud-rate?  Like have
some customizable variable or somesuch?  If implemented in a
backward-compatible manner, that could be good progress, I think.



  reply	other threads:[~2020-10-23 11:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 21:11 Relevance of `baud-rate' in the 2020s? Stefan Kangas
2020-10-23  3:45 ` Richard Stallman
2020-10-23  6:43 ` Eli Zaretskii
2020-10-23 10:21   ` Stefan Kangas
2020-10-23 11:05     ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ft65jj79.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.