From: Adam Spiers <emacs-devel@adamspiers.org>
To: emacs-devel mailing list <emacs-devel@gnu.org>
Subject: Re: custom-save-variables: pretty-printing long values
Date: Thu, 11 Apr 2013 20:07:13 +0100 [thread overview]
Message-ID: <20130411190713.GA16559@pacific.linksys.moosehall> (raw)
In-Reply-To: <jwvtxndm4cv.fsf-monnier+emacs@gnu.org>
On Thu, Apr 11, 2013 at 12:15:15PM -0400, Stefan Monnier wrote:
> > This simple tweak to cus-edit ensures that custom variable values
> > which are over 60 bytes long get written to `custom-file' using
> > `indent-pp-sexp'. For example:
>
> Looks like a good idea.
Thanks - I'll rebase on latest git master and resubmit to
bug-gnu-emacs.
prev parent reply other threads:[~2013-04-11 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 15:51 custom-save-variables: pretty-printing long values Adam Spiers
2013-04-11 16:15 ` Stefan Monnier
2013-04-11 19:07 ` Adam Spiers [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=20130411190713.GA16559@pacific.linksys.moosehall \
--to=emacs-devel@adamspiers.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).