From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, 65680-done@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: Fri, 29 Sep 2023 16:49:57 +0000 [thread overview]
Message-ID: <ZRcANbeyW0j_4LsK@ACM> (raw)
In-Reply-To: <83v8btywz3.fsf@gnu.org>
Hello, Eli.
On Fri, Sep 29, 2023 at 15:39:44 +0300, Eli Zaretskii wrote:
> > Date: Wed, 27 Sep 2023 15:12:37 +0000
> > Cc: Eli Zaretskii <eliz@gnu.org>
> > From: Alan Mackenzie <acm@muc.de>
> > I've implemented cl-print-string-length in cl-print.el, but not as a
> > customisable variable (for consistency with print-{length,level}). I
> > manipulate it in cl-print-string-with-limit by binding it to (- limit
> > 3), then multiplying it by ¾ at each successive trial printing.
> > I haven't yet made any amendment to the CL manual.
> Please do.
It seems that cl-print.el is entirely undocumented in the CL manual.
I've opened bug #66267 for this. I intend to work on it in the coming
days.
> > Here's the patch I propose to commit:
> OK, modulo Stefan's comment.
I've committed it, and I'm closing bug #65680 with this post.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-09-29 16:49 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
[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 [this message]
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=ZRcANbeyW0j_4LsK@ACM \
--to=acm@muc.de \
--cc=65680-done@debbugs.gnu.org \
--cc=eliz@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).