From: Michael Heerdegen <michael_heerdegen@web.de>
To: Sebastian Miele <iota@whxvd.name>
Cc: 64835@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#64835: ‘describe-variable’ unconditionally let-binds ‘print-circle’ to t
Date: Sun, 06 Aug 2023 04:54:10 +0200 [thread overview]
Message-ID: <877cq8519p.fsf@web.de> (raw)
In-Reply-To: <87zg3lmf1v.fsf@whxvd.name> (Sebastian Miele's message of "Mon, 24 Jul 2023 18:42:09 +0200")
Sebastian Miele <iota@whxvd.name> writes:
> 2c18969c810f338d73beda592ee5af7103132e97
> Author: Stefan Monnier <monnier@iro.umontreal.ca>
> AuthorDate: Thu Mar 2 02:08:08 2017 -0500
>
> * lisp/help-fns.el (describe-variable): Use cl-print for the value
> [...]
>
> (describe-variable 'ispell-dictionary-alist)
>
> The display of the value in my machine contains, e.g., "(nil #1# #2# #3#
> t #4# nil utf-8)".
> [...]
> I do not see the reason for hard-coding ‘print-circle’ to t in
> ‘describe-variable’.
I think I agree. Both values might be the optimum in different cases.
But most users are probably never interested in shared structures, some
will even be confused. And those that are interested also know how to
print using print-circle enabled themselves.
Stefan, would it be ok to turn off `print-circle' for
`describe-variable' again, or would this break something in the new
code?
TIA,
Michael.
next prev parent reply other threads:[~2023-08-06 2:54 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
2023-08-06 2:54 ` Michael Heerdegen [this message]
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=877cq8519p.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=64835@debbugs.gnu.org \
--cc=iota@whxvd.name \
--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).