unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 'Drew Adams'
	<IMCEAORCL-drew+2Eadams+40oracle+2Ecom@namprd10.prod.outlook.com>,
	Lars Ingebrigtsen <larsi@gnus.org>
Cc: "14754@debbugs.gnu.org" <14754@debbugs.gnu.org>
Subject: bug#14754: 24.3.50; `C-h v' needs to fill wide `pp' lines (493 chars wide?!)
Date: Thu, 9 Jun 2022 16:36:26 +0000	[thread overview]
Message-ID: <SJ0PR10MB54885D6AAF5588620A453053F3A79@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: 4be36dd8-7c8c-4e9a-a7b6-b036f624de8a@default

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

This was closed as fixed in 29.1.  I don't have
that release, so I can't check this.

I hope this problem is fixed.  I was wrong about
the solution being to just fill.  That would be
catastrophic for some variable values, such as
for `directory-listing-before-filename-regexp',
where SPC chars are significant etc.  (For that
var the result of filling ended up, in effect,
replacing the SPC before the + at the end of the
regexp with just a newline.)

Some enhancement of pretty-printing, to control
(or at least to try to control) the width is
needed.  Maybe that's what's been implemented as
part of the fix.  If so, great.

The problem, in general, is this:

* We need to be able to print (e.g. pretty-print)
  any Lisp value.

* Buffer `*Help*' should not have lines longer
  than what the style convention calls for.

Trying to finesse those two different rules is
the difficulty.  If you've come up with a good
solution, bravo.


[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 14413 bytes --]

             reply	other threads:[~2022-06-09 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 16:36 Drew Adams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-06-30  7:10 bug#14754: 24.3.50; `C-h v' needs to fill wide `pp' lines (493 chars wide?!) Drew Adams
2013-07-01 17:07 ` Drew Adams
2014-02-08  6:38 ` Lars Ingebrigtsen
2014-02-10  3:56   ` Drew Adams

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=SJ0PR10MB54885D6AAF5588620A453053F3A79@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=14754@debbugs.gnu.org \
    --cc=IMCEAORCL-drew+2Eadams+40oracle+2Ecom@namprd10.prod.outlook.com \
    --cc=larsi@gnus.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).