From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: acm@muc.de, 65680@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#65680: cl-print-to-string-with-limit erroneously imposes a maximum print-length of 50
Date: Thu, 21 Sep 2023 21:33:53 +0300 [thread overview]
Message-ID: <83il838jfy.fsf@gnu.org> (raw)
In-Reply-To: <ZQx4bskZ7fWGOwRL@ACM> (message from Alan Mackenzie on Thu, 21 Sep 2023 17:07:58 +0000)
> Cc: acm@muc.de, 65680@debbugs.gnu.org
> Date: Thu, 21 Sep 2023 17:07:58 +0000
> From: Alan Mackenzie <acm@muc.de>
>
> > [ 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.
TTTT, 2 days is too short a time to assume no one has anything to say
about a change. I had a busy day and just couldn't get to it, before
I saw you have already installed it.
> 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.
500 is too large a value, my vote is for 200 at most.
next prev parent reply other threads:[~2023-09-21 18:33 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
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 [this message]
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83il838jfy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65680@debbugs.gnu.org \
--cc=acm@muc.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.