From: Bob Proulx <bob@proulx.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Default value of recenter-redisplay
Date: Sun, 29 Apr 2018 11:07:29 -0600 [thread overview]
Message-ID: <20180429103922929100276@bob.proulx.com> (raw)
In-Reply-To: <831seyt50x.fsf@gnu.org>
Eli Zaretskii wrote:
> > John Shahid wrote:
> > I'm wondering why the default value of the variable is set to `tty' ?
>
> Because one important interactive use of 'recenter' is to redraw the
> screen to eliminate display corruptions due to all kinds of unrelated
> messages being dumped on the console. When this variable and the
> related feature was introduced, RMS explicitly asked not to change the
> then default behavior on TTY's, see
>
> http://lists.gnu.org/archive/html/emacs-devel/2009-06/msg00416.html
I am compelled to say (because otherwise someone will argue that no
one complained about the change) that even if other people don't ever
see output emitted to their tty outside of emacs that I do still
routinely run into the case. I see shutdown warnings or kernel
messages from martian IP packets or whatwever as there are many things
that write to the tty. I rely upon C-l a lot.
Obviously a graphical X11 window does not have external processes
modifying it and does not need to be redisplayed.
> > Also, is it safe to set the variable to `nil' ?
>
> If you don't care about fixing corrupted display on TTYs (or never
> experienced that), you can safely change it to nil.
>
> > If it is safe, can we change the default value to `nil' in order to
> > have a better terminal experience ?
A better terminal experience is that C-l can be used after several
lines have been written to the tty by outside processes. Keeping it
the same as with other terminal programs such as bash, vi, vim, less,
mutt, and so forth. Making C-l work differently from those other
programs makes for a worse terminal experience. A positive transfer
of learning across many programs.
> Why does it have to change by default? I generally find arguments
> about default values to be waste of time and energy, since anyone who
> doesn't like the default can change it for them.
Changing defaults is painful and frustrating to people (often me) who
make use of the defaults. It makes the feature one that is required
to be configured before it can be used. Which contributes to making
emacs hard to learn for newcomers. Which perpetuates the stereotype
that emacs is too arcane. That's bad.
And as long as I am here I am also one of those people who didn't like
the change from recenter to recenter-top-bottom. I added this to my
key bindings to avoid it.
(global-set-key "\C-l" 'recenter) ; originally recenter, now annoyingly recenter-top-bottom
Bob
next prev parent reply other threads:[~2018-04-29 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 14:10 Default value of recenter-redisplay John Shahid
2018-04-29 14:47 ` Amos Bird
2018-04-29 15:02 ` Göktuğ Kayaalp
2018-04-29 15:18 ` Eli Zaretskii
2018-04-29 17:07 ` Bob Proulx [this message]
2018-04-29 17:29 ` tomas
2018-04-29 19:50 ` Drew Adams
2018-04-29 17:36 ` Drew Adams
2018-04-29 17:46 ` Eli Zaretskii
2018-04-29 22:11 ` John Shahid
2018-04-30 12:38 ` Stefan Monnier
2018-05-01 1:18 ` unknown
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=20180429103922929100276@bob.proulx.com \
--to=bob@proulx.com \
--cc=help-gnu-emacs@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.
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).