From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 11934@debbugs.gnu.org
Subject: bug#11934: 24.1; provide variable for pp.el to control max display width
Date: Thu, 28 Apr 2016 17:53:43 +0200 [thread overview]
Message-ID: <87bn4tafw8.fsf@gnus.org> (raw)
In-Reply-To: <EEDE71D0ED764E5DACDF22CF18007444@us.oracle.com> (Drew Adams's message of "Fri, 13 Jul 2012 07:48:04 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> The request is to provide a variable that controls the width of the
> displayed expression, or at least tries to as much as possible.
>
> For example, I have a variable whose value is this:
>
> (bbdb-complete-name comint-completion-at-point
> comint-dynamic-complete-filename comint-replace-by-expanded-filename
> ess-complete-object-name gud-gdb-complete-command Info-goto-node
> Info-index Info-menu lisp-complete-symbol lisp-completion-at-point
> minibuffer-default-add-completions read-char-by-name read-color
> read-from-minibuffer read-string recentf-make-menu-items)
[...]
> It would be good to be able to bind a max-width variable that lets the
> pp functions know that it is better, if possible, to insert newline
> chars to try to keep the width below that var's value.
I agree. What pp does now with simple lists isn't optimal.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-28 15:53 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 [this message]
2016-04-29 14:14 ` Michael Heerdegen
2016-04-29 14:24 ` Lars Ingebrigtsen
2016-04-29 17:47 ` Drew Adams
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=87bn4tafw8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=11934@debbugs.gnu.org \
--cc=drew.adams@oracle.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).