unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Yates <john@yates-sheets.org>
To: David Kastrup <dak@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Feature Request: Per-package custom save files?
Date: Sat, 21 Jun 2014 12:45:17 -0400	[thread overview]
Message-ID: <CAJnXXoh=5DX7B4qWjsJArjPrEo9dTCq2S=9P3ucuK0dxDWcKRQ@mail.gmail.com> (raw)
In-Reply-To: <87ppi25kbo.fsf@fencepost.gnu.org>

On Sat, Jun 21, 2014 at 11:55 AM, David Kastrup <dak@gnu.org> wrote:
>
> ...  Doing a sorted cleanup should be reasonably possible using
>
> M-x customize-saved RET

Yuck.  That is a horrible experience, in some ways better but also in
some ways worse than auditing one's custom file manually.

I agree with some of T. V. Raman's sentiments.  I like to use the
customize interface for the purpose of exploring the options offered
by a package.  Still long ago I discovered that the customize-file
provides no help for understanding one's configuration.  My approach
is to document all of my customizations in my .emacs file.  I still
use custom to load those customizations but I automatically compare
the contents of my two file to confirm that they are in sync.  You can
see this in my .emacs on github
(https://github.com/jsyjr/MyConfiguration/blob/master/.emacs, most
easily viewed with folding mode).  See in particular the sections near
the top of the file labeled:
  ;;{{{ Customization auditing framework
  ;;{{{ Load customizations
And the section near the bottom of the file labeled:
  ;;{{{ Audit customizations

T. V. Raman points out the phenomenon of having explicit
customizations recorded that merely duplicate defaults.  Currently my
scheme does not address this issue.

/john



  reply	other threads:[~2014-06-21 16:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-21 15:42 Feature Request: Per-package custom save files? T. V. Raman
2014-06-21 15:55 ` David Kastrup
2014-06-21 16:45   ` John Yates [this message]
2014-06-21 17:19 ` Stefan Monnier
2014-06-23 16:52   ` T.V Raman
2014-06-23 19:30     ` chad
2014-06-23 21:11       ` T.V Raman
2014-06-23 21:11     ` Stefan Monnier
2014-06-23 21:17       ` T.V Raman
2014-06-24  1:24         ` Stefan Monnier
2014-06-24 14:55           ` raman
2014-06-24 17:19             ` Stefan Monnier
2014-06-25 16:40               ` T.V Raman
2014-06-25 17:54                 ` Stefan Monnier
2014-06-25 18:01                   ` T.V Raman

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='CAJnXXoh=5DX7B4qWjsJArjPrEo9dTCq2S=9P3ucuK0dxDWcKRQ@mail.gmail.com' \
    --to=john@yates-sheets.org \
    --cc=dak@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).