From: David Kastrup <dak@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Sean Allred <code@seanallred.com>,
bruce.connor.am@gmail.com, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Incorporating caching into defgroup/defcustom/defvar for Emacs 25
Date: Mon, 02 Feb 2015 14:06:40 +0100 [thread overview]
Message-ID: <87vbjkv4wv.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87wq40pit3.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Mon, 02 Feb 2015 22:03:04 +0900")
"Stephen J. Turnbull" <stephen@xemacs.org> writes:
> Artur Malabarba writes:
> > On 2 Feb 2015 01:07, "Stephen J. Turnbull" <stephen@xemacs.org> wrote:
>
> > > Why not? Custom provides a "reset" functionality if the user *wants*
> > > to reset. It's not clear to me that a user wouldn't want changes to
> > > customizable variables to persist.
> >
> > I wasn't saying defcustoms shouldn't be persistent, I was just
> > saying they already have a great mechanism for that so they don't
> > need to use this caching mechanism that is being suggested for
> > internal variables.
>
> Yes, they might. A user who is testing out a new custom setting might
> like the setting to persist without explicitly saving it if Emacs
> crashes or he runs out of memory and needs to stop and restart Emacs,
> or something like that.
Personally, I very much prefer it if my experiments do not follow me
around for the rest of my life. That is, I _like_ to be able to restart
Emacs and have it return to a well-known state.
--
David Kastrup
next prev parent reply other threads:[~2015-02-02 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 16:46 Incorporating caching into defgroup/defcustom/defvar for Emacs 25 Sean Allred
2015-02-01 16:56 ` Sean Allred
2015-02-02 1:07 ` Stephen J. Turnbull
2015-02-02 10:08 ` Artur Malabarba
2015-02-02 13:03 ` Stephen J. Turnbull
2015-02-02 13:06 ` David Kastrup [this message]
2015-02-02 13:16 ` Artur Malabarba
2015-02-02 14:24 ` Drew Adams
2015-02-02 18:26 ` Stefan Monnier
2015-02-02 20:48 ` Artur Malabarba
2015-02-02 23:30 ` Stefan Monnier
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=87vbjkv4wv.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=code@seanallred.com \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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).