unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bob Proulx <bob@proulx.com>
Cc: emacs-devel@gnu.org
Subject: Re: Stop fiddling with my preferences
Date: Mon, 01 Dec 2014 17:54:18 +0200	[thread overview]
Message-ID: <83d2838ixh.fsf@gnu.org> (raw)
In-Reply-To: <20141130235724153372947@bob.proulx.com>

> Date: Mon, 1 Dec 2014 00:15:53 -0700
> From: Bob Proulx <bob@proulx.com>
> 
> Eli Zaretskii wrote:
> > Roland Lutz wrote:
> > > operating systems, but does this make it appropriate for Emacs?  One of 
> > > the reasons I'm using mature software is exactly that I *don't* have to be 
> > > worried with each new version that ESC won't stop playing animated GIFs 
> > > any more, etc.
> > 
> > We change user-visible behavior in response to user demand, not
> > because Emacs is immature.  User demands and expectations change with
> > time, and Emacs cannot stay with old defaults forever.
> 
> I often hear developers saying this.  But I rarely hear users asking
> for these (mis)features.

You should read this list more frequently, then.  Typically, each such
decision (or indecision) is accompanied by a very long discussion
here, with core developers usually _resisting_ radical changes that
break old habits.  We, too, use Emacs, you know.

Here's a discussion related to that particular (mis)feature.

  http://lists.gnu.org/archive/html/emacs-devel/2013-10/msg00407.html

> Therefore what it feels like is actually happening is that when
> developers want to do something they just do it and claim that users
> want it.  When they don't want to do it then they claim they can't
> because of backward compatibility.

That's extremely unfair.  The truth is almost the opposite.  I invite
you to read the archives of this list and see for yourself.  Perhaps
others could point to additional discussions regarding similar changes
(turning on font-lock globally comes to mind).



  parent reply	other threads:[~2014-12-01 15:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23 15:35 Stop fiddling with my preferences Roland Lutz
2014-11-23 16:27 ` Eric S. Raymond
2014-11-23 17:32   ` Eli Zaretskii
2014-11-23 17:45     ` Roland Lutz
2014-11-23 17:59       ` Eli Zaretskii
2014-11-23 16:42 ` Eli Zaretskii
2014-11-23 17:25   ` Fabrice Popineau
2014-11-25 14:25     ` Sebastian Wiesner
2014-11-25 16:47       ` Eli Zaretskii
2014-11-25 17:12         ` Sebastian Wiesner
2014-11-25 17:29           ` Eli Zaretskii
2014-11-25 17:30             ` Sebastian Wiesner
2014-11-25 19:18               ` Fabrice Popineau
2014-12-01  7:15   ` Bob Proulx
2014-12-01 13:42     ` Stefan Monnier
2014-12-01 15:54     ` Eli Zaretskii [this message]
2014-11-30 14:02 ` Stefan Monnier
2014-11-30 14:15   ` joakim
2014-11-30 15:00     ` Eric Abrahamsen
2014-11-30 14:31   ` H. Dieter Wilhelm
2014-11-30 15:43     ` Eli Zaretskii
2014-11-30 19:32       ` H. Dieter Wilhelm

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=83d2838ixh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bob@proulx.com \
    --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).