From: Stefan Monnier <monnier@iro.umontreal.ca>
To: raman@google.com (T.V Raman)
Cc: emacs-devel@gnu.org
Subject: Re: Feature Request: Per-package custom save files?
Date: Wed, 25 Jun 2014 13:54:33 -0400 [thread overview]
Message-ID: <jwvha38sxrh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <21418.64359.745530.259301@retriever.mtv.corp.google.com> (T. V. Raman's message of "Wed, 25 Jun 2014 09:40:07 -0700")
> when custom settings that are large s-expressions break during
> save --
If you still have such a broken file, please M-x report-emacs-bug to see
what we could do to avoid these problems.
Maybe for such important files that aren't saved very often, it would be
worthwhile to double-check that what we're about to write is what we
intended to write (i.e. try to read it back before saving).
> say the partial sexp gets saved, the whole file breaks.
Right, in some cases, indeed, having several files could confine
the breakage. In that case, the specific way the list is broken up
doesn't matter that much, which is good.
Maybe we could simply allow custom-file to be a function which takes the
list of settings to save and splits them into a list of (FILE
. SETTINGS).
Stefan
next prev parent reply other threads:[~2014-06-25 17:54 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
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 [this message]
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=jwvha38sxrh.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=raman@google.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).