unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: John Shahid <jvshahid@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 31325@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#31325: 27.0.50; PROPOSAL: introduce a new function to recenter without redisplaying the frame
Date: Sun, 1 Jul 2018 13:17:25 -0700 (PDT)	[thread overview]
Message-ID: <7ac98ea5-23c8-456a-8c40-18c703bea617@default> (raw)
In-Reply-To: <87r2kmyikh.fsf@gmail.com>

Sorry, but I've not been following this bug thread.
I took only a (very) quick look at it, at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31325.

It looks like you are changing the default behavior of
`recenter', which is a backward-incompatible change.

Am I right about that, so that all Lisp calls of that
function would now need to be changed, to add a non-nil
2nd arg in order to keep the same behavior?

The reported bug was only about a problem for Emacs in
a terminal, right?  Can't it just be fixed to DTRT in
that case, without changing so much in the definition
and behavior of the function?

Apologies if I misunderstood something.  I really only
glanced at the thread.  But if what thought I saw is
right, is this really the right fix?

The behavior of `recenter' has remained pretty much
unchanged since, well, _forever_.  And when I came up
with `recenter-top-bottom' the idea was explicitly
_not_ to change the behavior of `recenter'.

And in the old days people used Emacs mainly (and
originally, only) in the terminal.  Why is the terminal
behavior suddenly considered to be bugged?  Or given
that it is bugged - is changing the default behavior
the best fix?

Please ignore, if my understanding is wrong or my
comments on this are not helpful.





  reply	other threads:[~2018-07-01 20:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01  0:48 bug#31325: 27.0.50; PROPOSAL: introduce a new function to recenter without redisplaying the frame John Shahid
2018-05-08  1:37 ` Stefan Monnier
2018-06-28 13:27   ` John Shahid
2018-06-30  9:45     ` Eli Zaretskii
2018-06-30 20:20       ` John Shahid
2018-07-01  9:05         ` martin rudalics
2018-07-01 13:17           ` John Shahid
2018-07-01 16:22             ` Eli Zaretskii
2018-07-01 16:54               ` John Shahid
2018-07-01 17:03                 ` Eli Zaretskii
2018-07-01 17:14                   ` Eli Zaretskii
2018-07-01 17:25                     ` John Shahid
2018-07-01 20:17                       ` Drew Adams [this message]
2018-07-01 20:56                         ` John Shahid
2018-07-01 23:04                           ` Drew Adams
2018-07-02  2:27                             ` John Shahid
2018-07-02 15:18                               ` Eli Zaretskii
2018-07-01 17:18                   ` John Shahid
2018-07-01 18:05                     ` Eli Zaretskii
2018-07-01 18:58                       ` John Shahid
2018-07-02 15:22                         ` Eli Zaretskii
2018-07-02 20:38                           ` John Shahid
2018-07-03  8:49                             ` Robert Pluim
2018-07-03 16:38                             ` John Shahid
2018-07-07  9:09                               ` Eli Zaretskii

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=7ac98ea5-23c8-456a-8c40-18c703bea617@default \
    --to=drew.adams@oracle.com \
    --cc=31325@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jvshahid@gmail.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).