From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Michael Heerdegen <michael_heerdegen@web.de>
Cc: 11934@debbugs.gnu.org
Subject: bug#11934: 24.1; provide variable for pp.el to control max display width
Date: Fri, 29 Apr 2016 10:47:36 -0700 (PDT) [thread overview]
Message-ID: <9eca35ee-4253-4560-9406-ba9ac1dc9584@default> (raw)
In-Reply-To: <8737q47ata.fsf@gnus.org>
> Well, pp isn't really designed for handling code.
Maybe you mean that it doesn't do a good enough job
of it? I think it is designed for handling code, as much
as for handling data. It just doesn't handle them differently.
Lisp code and Lisp data structures are not very different,
though yes, we generally follow some code-specific formatting
conventions - and pp.el does not bother with those (as it
cannot know whether you want to consider the sexp as code
or data).
> I pp'd a function at random... it may be pretty, but it
> sure is unusual for code...
It's pretty-printed. And not too bad.
> So I don't really think that's a consideration here.
If you mean that pp.el shouldn't bother to do something
special for code then I agree. At least until/unless
we add an optional arg to indicate the intention to
interpret the result as code and not data.
next prev parent reply other threads:[~2016-04-29 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 14:48 bug#11934: 24.1; provide variable for pp.el to control max display width Drew Adams
2016-04-28 15:53 ` Lars Ingebrigtsen
2016-04-29 14:14 ` Michael Heerdegen
2016-04-29 14:24 ` Lars Ingebrigtsen
2016-04-29 17:47 ` Drew Adams [this message]
2016-04-29 17:44 ` Drew Adams
2016-04-29 19:26 ` Michael Heerdegen
2016-04-29 19:37 ` Drew Adams
2021-11-05 14:27 ` 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=9eca35ee-4253-4560-9406-ba9ac1dc9584@default \
--to=drew.adams@oracle.com \
--cc=11934@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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).