unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: raman@google.com (T.V Raman)
To: monnier@iro.umontreal.ca
Cc: tv.raman.tv@gmail.com, emacs-devel@gnu.org, raman@google.com
Subject: Re: Feature Request: Per-package custom save files?
Date: Mon, 23 Jun 2014 14:17:24 -0700	[thread overview]
Message-ID: <21416.39268.648625.775759@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <jwvvbrrqqn4.fsf-monnier+emacs@gnu.org>

HMM, good point 

What I'm mostly looking for is  to have a modular collection of
custom files -- note -- here I'm explicitly talking about
customizations for add-on packages -- not for built-ins.  

Stefan Monnier writes:
 > > 2. My thought around factoring out custom settings into a
 > > canonical per-package custom-settings file was to achieve the
 > > second goal -- not loading settings for packages you dont use --
 > 
 > That doesn't really sound like a goal to me.  More specifically, I'd
 > like to know why you care about loading settings you don't use.
 > 
 > IOW, let's imagine we change it so that the settings are only loaded
 > once they're needed.  How will you tell the difference?
 > 
 > 
 >         Stefan



  reply	other threads:[~2014-06-23 21:17 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
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 [this message]
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=21416.39268.648625.775759@retriever.mtv.corp.google.com \
    --to=raman@google.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).