From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 7524@debbugs.gnu.org
Subject: bug#7524: 24.0.50; backquote converts newlines in strings to "\n"
Date: Thu, 23 Dec 2010 14:53:39 -0800 [thread overview]
Message-ID: <000B33E7F2484128B3849AD9541163B6@us.oracle.com> (raw)
In-Reply-To: <jwvhbexqskx.fsf-monnier+emacs@gnu.org>
> And yes, Custom should probably try to wrap lines somehow in
> such cases (e.g. pretty-print the sexp).
Any chance this pretty-printing will actually get done?
The utility goes well beyond `\n' in strings.
Just now I created a defcustom whose :type is
(repeat (restricted-sexp
:tag "Keymap"
:match-alternatives (keymapp 'nil)))
And you cannot believe how ugly such a value is, not to mention how error-prone
editing it would be! Regardless of what one might think of trying to use a
keymap value this way, the point is that any non-trivial Lisp sexp needs to be
pretty-printed.
`restricted-sexp can be a quick-and-dirty substitute for defining the widgets
needed to get a new :type construct. But it is rendered pretty unusable without
(at least) pretty-printing.
There are likely to be plenty of Lisp values for which pretty-printing would
help. Any chance you will add this to the Emacs TO-DO list?
next prev parent reply other threads:[~2010-12-23 22:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 6:10 bug#7524: 24.0.50; backquote converts newlines in strings to "\n" Drew Adams
2010-12-01 16:04 ` Stefan Monnier
2010-12-01 16:40 ` Drew Adams
2010-12-01 18:07 ` Stefan Monnier
2010-12-01 18:42 ` Drew Adams
2010-12-23 22:53 ` Drew Adams [this message]
2010-12-06 17:56 ` Stefan Monnier
2010-12-06 18:06 ` Drew Adams
2010-12-06 20:16 ` Stefan Monnier
2010-12-06 21:45 ` Drew Adams
2010-12-07 3:42 ` Stefan Monnier
2010-12-06 18:10 ` Drew Adams
2010-12-06 19:58 ` Lennart Borgman
2010-12-06 21:38 ` Drew Adams
2010-12-06 21:45 ` Lennart Borgman
2020-10-22 12:24 ` Mauro Aranda
2020-10-22 12:31 ` Lars Ingebrigtsen
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=000B33E7F2484128B3849AD9541163B6@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=7524@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).