unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 5974@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
	Nicolas Richard <youngfrog@members.fsf.org>
Subject: bug#5974: 23.1.95; enabling disabled cmd & saving doesn't respect `custom-file'
Date: Fri, 29 Apr 2016 16:11:43 -0700 (PDT)	[thread overview]
Message-ID: <c854f27d-5f53-4fc8-a761-7ecfd7c37d32@default> (raw)
In-Reply-To: <87wpngkpkg.fsf@gnus.org>


> It's not a side discussion.  The `put' things are not going to move to
> `custom-file', because they have nothing to do with Custom.

Good point.  I retract my objection.

> But they might "in effect" move to `custom-file' if we change how they
> are implemented.

Actually, now that you've pointed out that they have nothing to
do with Customize (options, faces), I wonder whether where they
should go.

The point of `custom-file' is, on the one hand, to keep automatically
written Lisp code from mixing with hand-coded stuff, in ~/.emacs.

On the other hand, its point is to gather in one place only stuff
that is managed by Customize.

Typically (so far), we use other files for other automatically
written Lisp code: bookmarks, desktops, package stuff, savehist,
saveplace,...

Especially since we now have an Emacs-specific default directory
for such things, a separate file seems to make sense - not
`custom-file' (since this is not managed by Customize) but something
else.

As for the suggestion that this be handled by Customize: A priori,
I'm not too hot for that idea.  I think it has enough trouble with
options and faces. ;-)  But maybe someone has a good reason why it
should be Customize that manages these things.





      reply	other threads:[~2016-04-29 23:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 16:22 bug#5974: 23.1.95; enabling disabled cmd & saving doesn't respect `custom-file' Drew Adams
2010-04-19 17:06 ` Drew Adams
2010-04-19 17:22 ` Stefan Monnier
2016-04-27 21:53   ` Lars Ingebrigtsen
2016-04-28 10:41     ` Nicolas Richard
2016-04-28 22:57       ` Lars Ingebrigtsen
2016-04-28 23:08         ` Lars Ingebrigtsen
2016-04-29 14:21         ` Nicolas Richard
2016-04-29 14:30           ` Lars Ingebrigtsen
2016-04-29 16:31             ` Drew Adams
2016-04-29 20:20               ` Nicolas Richard
2016-04-29 22:32                 ` Drew Adams
2016-04-29 22:39                   ` Lars Ingebrigtsen
2016-04-29 23:11                     ` Drew Adams [this message]

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=c854f27d-5f53-4fc8-a761-7ecfd7c37d32@default \
    --to=drew.adams@oracle.com \
    --cc=5974@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=youngfrog@members.fsf.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).