From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: acm@muc.de, 65680@debbugs.gnu.org
Subject: bug#65680: cl-print-to-string-with-limit erroneously imposes a maximum print-length of 50
Date: Thu, 21 Sep 2023 17:07:58 +0000 [thread overview]
Message-ID: <ZQx4bskZ7fWGOwRL@ACM> (raw)
In-Reply-To: <jwvpm2bh5bi.fsf-monnier+emacs@gnu.org>
Hello, Stefan.
On Thu, Sep 21, 2023 at 12:16:57 -0400, Stefan Monnier wrote:
> Alan Mackenzie [2023-09-01 14:17:12] wrote:
> > Hello, Emacs.
> > In cl-print-to-string-with-limit appears the following binding:
> > (print-length (cond
> > ((null limit) nil)
> > ((eq limit t) print-length)
> > (t (min limit 50))))
> > ^^^^^^^^^^^^
> > .. This has the effect of ignoring the parameter LIMIT (unless it is
> > very small) and instead truncating the printed size to 50. There is a
> > similar mechanism to limit print-level to 8.
> > Although the doc string doesn't explicitly say it won't truncate like
> > this, it kind of implies that LIMIT is the size it will truncate to.
> > This excessive truncation is a bug.
> See also bug#34183.
> > .. I propose fixing this bug by removing these limits on print-length and
> > print-level in cl-print-to-string-with-limit.
> Sounds a bit drastic. Strings can be obnoxiously long, so it's
> important for cl-print to be able to truncate them.
There is clearly no human-sized bound on string lengths, so they can
indeed be very long. Most of the time they're not. But they are very
frequently longer than 50 characters.
> [ IOW, I'm not happy with commit
> 761f8901fffdb155cbcc7f3b5a2329161c2c1826. ]
Well I did post about it to emacs-devel on Sunday and Monday, asking if
anybody had any objection. Nobody, not even you, responded.
I still believe that not truncating strings is better than truncating
them to the minute length of 50. In fact, why truncate strings at all in
cl-prin1? They're not truncated in prin1, etc. The reason for
truncating lists and vectors is to prevent infinite printing when there's
a circular list or vector, something which cannot happen with a string.
If somebody doesn't want a string longer that 50 to get printed, then she
shouldn't call cl-prin1 with it.
The mistake in Emacs before my patch was a category error: wrongly
believing that print-length applies to a string length too. It doesn't.
String lengths are a completely different kettle of fish from list
lengths.
To solve this problem properly, we need, as Eli has suggested, a separate
variable called something like print-string-length, to be set
independently of print-length (and print-level). A sensible value for
this variable in printing backtraces might be, say, 500.
> Stefan
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-09-21 17:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 14:17 bug#65680: cl-print-to-string-with-limit erroneously imposes a maximum print-length of 50 Alan Mackenzie
2023-09-19 10:32 ` Alan Mackenzie
2023-09-21 16:16 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21 16:36 ` Eli Zaretskii
2023-09-21 17:07 ` Alan Mackenzie [this message]
2023-09-21 17:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21 19:22 ` Drew Adams
2023-09-21 20:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21 18:33 ` Eli Zaretskii
[not found] ` <ZQ1m766tulSqvuC6@ACM>
[not found] ` <83msxe779i.fsf@gnu.org>
[not found] ` <ZQ2JVhy-e8NpCJqq@ACM>
[not found] ` <837coi74ia.fsf@gnu.org>
[not found] ` <jwva5tefif5.fsf-monnier+emacs@gnu.org>
[not found] ` <ZRRGZaRf3WU9z6m_@ACM>
[not found] ` <83v8btywz3.fsf@gnu.org>
2023-09-29 16:49 ` Alan Mackenzie
2023-09-29 16:53 ` Eli Zaretskii
2023-10-03 2:11 ` Michael Heerdegen
2023-10-03 9:18 ` Alan Mackenzie
2023-10-03 10:26 ` Alan Mackenzie
2023-10-03 23:35 ` Michael Heerdegen
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=ZQx4bskZ7fWGOwRL@ACM \
--to=acm@muc.de \
--cc=65680@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).