From: Eli Zaretskii <eliz@gnu.org>
To: Karl Fogel <kfogel@red-bean.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Should `revert-buffer' preserve text-scaling by default?
Date: Tue, 03 Dec 2019 18:09:05 +0200 [thread overview]
Message-ID: <83muc9jsri.fsf@gnu.org> (raw)
In-Reply-To: <87fti2s6nu.fsf@red-bean.com> (message from Karl Fogel on Mon, 02 Dec 2019 16:29:25 -0600)
> From: Karl Fogel <kfogel@red-bean.com>
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> Date: Mon, 02 Dec 2019 16:29:25 -0600
>
> What is the process by which we might eventually decide to change the default to non-nil (that is, to *not* resetting modes)?
>
> In other words, how will the mere passage of time affect our willingness to change the default interactive behavior?
By letting people try this and tell us via bug reports and other
communications channels that they'd like this to be the default.
next prev parent reply other threads:[~2019-12-03 16:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 20:24 Should `revert-buffer' preserve text-scaling by default? Karl Fogel
2019-11-29 20:39 ` Eli Zaretskii
2019-11-29 21:02 ` Karl Fogel
2019-11-30 7:24 ` Eli Zaretskii
2019-11-29 21:09 ` Stefan Monnier
2019-11-29 21:20 ` Karl Fogel
2019-11-30 7:22 ` Eli Zaretskii
2019-12-01 8:15 ` Karl Fogel
2019-12-01 9:47 ` Stefan Kangas
2019-12-01 10:24 ` Juanma Barranquero
2019-12-01 17:38 ` Eli Zaretskii
2019-12-01 10:27 ` Michael Albinus
2019-12-01 17:35 ` Karl Fogel
2019-12-01 18:25 ` Stefan Monnier
2019-12-02 2:01 ` Karl Fogel
2019-12-02 16:15 ` Eli Zaretskii
2019-12-02 17:19 ` Karl Fogel
2019-12-02 17:42 ` Eli Zaretskii
2019-12-02 22:29 ` Karl Fogel
2019-12-02 22:49 ` Stefan Monnier
2019-12-03 0:36 ` Karl Fogel
2019-12-03 16:11 ` Eli Zaretskii
2019-12-03 16:10 ` Eli Zaretskii
2019-12-03 16:09 ` Eli Zaretskii [this message]
2019-12-03 17:35 ` Karl Fogel
2019-12-01 21:49 ` Juri Linkov
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=83muc9jsri.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=monnier@iro.umontreal.ca \
/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).