unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "T. V. Raman" <raman@google.com>
To: emacs-devel@gnu.org
Cc: tv.raman.tv@gmail.com
Subject: Feature Request: Per-package custom save files?
Date: Sat, 21 Jun 2014 08:42:53 -0700	[thread overview]
Message-ID: <21413.43005.992475.896234@lapdog.roam.corp.google.com> (raw)

As a long-term emacs user, I switched to custom about 11 years
ago.

I let custom save its settings to a .customize-emacs -- rather
than let it add to my .emacs so I can continue to edit my .emacs
by hand.

This means that I've let custom manage .customize-emacs -- that
is nice; however looking at it now, I see that that file has
become huge.  What's more  -- there are a lot of saved settings
in there that are likely now obsolete/irrelevant -- also some
settings that needed to be set explicitly in early versions of
packages is now achieved by not doing anything since the defaults
do the right thing. Finally,  custom ends up loading
customizations for *every* package you've ever seen -- including
ones that you use at present, ones that you autoload and ones
that you dont have around any more.

So feature request:

Could we arrange for customize to save package specific settings
in a package-specific customizations file?  The present one
custom file that binds them all feels like the Windows Registry:-)
-- 

-- 



             reply	other threads:[~2014-06-21 15:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-21 15:42 T. V. Raman [this message]
2014-06-21 15:55 ` Feature Request: Per-package custom save files? David Kastrup
2014-06-21 16:45   ` John Yates
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=21413.43005.992475.896234@lapdog.roam.corp.google.com \
    --to=raman@google.com \
    --cc=emacs-devel@gnu.org \
    --cc=tv.raman.tv@gmail.com \
    /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).