unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sebastian Miele <iota@whxvd.name>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 64835@debbugs.gnu.org
Subject: bug#64835: ‘describe-variable’ unconditionally let-binds ‘print-circle’ to t
Date: Mon, 24 Jul 2023 19:23:53 +0200	[thread overview]
Message-ID: <87wmyp8bbs.fsf@whxvd.name> (raw)
In-Reply-To: <83o7k1qm1g.fsf@gnu.org>

> From: Eli Zaretskii <eliz@gnu.org>
> Date: Mon, 2023-07-24 20:03 +0300
>
>> From: Sebastian Miele <iota@whxvd.name>
>> Date: Mon, 24 Jul 2023 18:42:09 +0200
>>
>> That was not the case in Emacs 28.  It seems to have been introduced
>> in the following commit:
>>
>>   2c18969c810f338d73beda592ee5af7103132e97
>>   Author:     Stefan Monnier <monnier@iro.umontreal.ca>
>>   AuthorDate: Thu Mar 2 02:08:08 2017 -0500
>>   Commit:     Stefan Monnier <monnier@iro.umontreal.ca>
>>   CommitDate: Thu Mar 2 02:08:32 2017 -0500
>>
>>   * lisp/help-fns.el (describe-variable): Use cl-print for the value
>>
>>   Use `pp-buffer' rather than `pp' so as to avoid calling prin1 twice.
>>
>> 2017 is a while ago.  The first pretest release of Emacs 28 was in
>> December 2021.  So the commit must have entered the current emacs-29
>> branch in some "non-linear" way.
>
> I don't think so.  I see this code in Emacs 28.1.  So I'm not sure why
> you didn't see this behavior in Emacs 28, if indeed it is caused by
> print-circle.

I must have made a mistake when I tested with Emacs 28 yesterday.  After
checking again, the behavior clearly is in Emacs 28, too.





  reply	other threads:[~2023-07-24 17:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24 16:42 bug#64835: ‘describe-variable’ unconditionally let-binds ‘print-circle’ to t Sebastian Miele
2023-07-24 17:03 ` Eli Zaretskii
2023-07-24 17:23   ` Sebastian Miele [this message]
2023-08-06  2:54 ` Michael Heerdegen
2023-08-08  3:00   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-08  3:55     ` Michael Heerdegen
2023-08-08 12:55       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-06 10:09 ` Mattias Engdegård
2023-08-15  2:55   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-15 12:24     ` Mattias Engdegård

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=87wmyp8bbs.fsf@whxvd.name \
    --to=iota@whxvd.name \
    --cc=64835@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).