unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ian Dunn <dunni@gnu.org>
Cc: cpitclaudel@gmail.com, emacs-devel@gnu.org
Subject: Re: Tabulated list recenter issue
Date: Thu, 13 Apr 2017 09:17:52 +0300	[thread overview]
Message-ID: <83k26oj0fj.fsf@gnu.org> (raw)
In-Reply-To: <87d1chgliu.fsf@escafil> (message from Ian Dunn on Wed, 12 Apr 2017 21:10:33 -0400)

> From: Ian Dunn <dunni@gnu.org>
> Cc: Clément Pit-Claudel <cpitclaudel@gmail.com>,
>  emacs-devel@gnu.org
> Date: Wed, 12 Apr 2017 21:10:33 -0400
> 
> If there are people that like the current behavior (obviously you're one
> of them), then I agree that my proposed changes should only be optional.

IME, after enough years have passed over a certain behavior, we have
no good ways of predicting whether someone or something out there
depend on it.  In our "arrogance" (pardon my French) we tried from
time to time to pretend that we do know, and changed the long-standing
behavior in backward-incompatible ways, only to discover later that
someone got hurt or that subtle hard-to-solve bugs emerged.

In general, I think it makes sense, in such a veteran package, to
always leave a "fire escape" for those who must have the old behavior,
as a matter of principle.  We should realize that we can no longer
change Emacs in arbitrary incompatible ways, not after 30-odd years of
history and many veteran users who have certain habits burnt into
their muscle memory.  We should make this part of our development
practice.

Thanks.



  reply	other threads:[~2017-04-13  6:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01  2:51 Tabulated list recenter issue Ian Dunn
2017-04-12  0:56 ` Ian Dunn
2017-04-12  6:03   ` Eli Zaretskii
2017-04-12  6:25     ` Clément Pit-Claudel
2017-04-12  7:15       ` Eli Zaretskii
2017-04-12 12:28         ` Clément Pit-Claudel
2017-04-12 12:44           ` Eli Zaretskii
2017-04-12 13:11             ` Clément Pit-Claudel
2017-04-12 14:06               ` Eli Zaretskii
2017-04-12 15:13                 ` Clément Pit-Claudel
2017-04-13  1:10                 ` Ian Dunn
2017-04-13  6:17                   ` Eli Zaretskii [this message]
2017-04-15 21:02                     ` Ian Dunn
2017-04-12 10:19   ` 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=83k26oj0fj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cpitclaudel@gmail.com \
    --cc=dunni@gnu.org \
    --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).