From: Eli Zaretskii <eliz@gnu.org>
To: Roland Lutz <rlutz-ml@hedmen.org>
Cc: emacs-devel@gnu.org
Subject: Re: Stop fiddling with my preferences
Date: Sun, 23 Nov 2014 18:42:32 +0200 [thread overview]
Message-ID: <831totswav.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1411231623120.4785@home.local>
> Date: Sun, 23 Nov 2014 16:35:37 +0100 (CET)
> From: Roland Lutz <rlutz-ml@hedmen.org>
>
> For the past few months, however, each time I upgraded to a new version of
> Emacs, something in the behavior changed.
The time between Emacs releases is not measured in months,
unfortunately, but in years.
> I had to figure out each time what it was that caused the change and
> how to compensate for it. This usually took me an hour or more
> since it isn't easily documented and most solutions suggested on the
> web have unwanted side-effects.
Changes in user-visible behavior are documented in etc/NEWS, together
with the description of how to get back old behavior. If you find
some change that isn't documented like that, please report that as a
bug.
> This sort of behavior changes is common among browsers and proprietary
> 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.
> How about a command like (use-defaults VERSION)?
From the menu bar, click Options->Customize Emacs->New Options, and
you will be able to see all the options that were added or changed
since some Emacs version.
> Also, I'd appreciate if the history of user-visible changes included the
> commands necessary to restore the previous behavior.
We already do that, see above. It should be in NEWS; if not, please
report as a bug.
next prev parent reply other threads:[~2014-11-23 16:42 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831totswav.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rlutz-ml@hedmen.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.