From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 55395@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#55395: What does (1 2 3 . #2) mean?
Date: Sat, 14 May 2022 09:45:15 -0400 [thread overview]
Message-ID: <jwvpmkgfd88.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <715F3D50-7D11-47CF-A34B-6532F1F508D7@acm.org> ("Mattias Engdegård"'s message of "Fri, 13 May 2022 22:01:44 +0200")
>> The main goal is to avoid inf-looping and the #NNN chosen is
>> somewhat arbitrary.
> It seems to have sort-of worked before and was broken, inadvertently and
> with the best intentions, by a later change.
>
> Additionally the #N value appears to be correct for other object types. For example,
>
> [a [b #1=[[c #1# d]]]]
>
> is printed as
>
> [a [b [[c #2 d]]]]
>
> which is consistent with the manual.
I do have the impression that it used to be "correct", but I can't
remember of a single time where I actually made use of that NNN.
And even if you know what it means and it works correctly, it's pretty
hard for a normal human to correctly count the depth starting from
the root.
I suspect if we want to "do better", printing "the beginning" of the
object to which we're looping (and saying explicitly that there's
a cycle) will be a lot more useful to the average user.
[ Or we could even print "the period" rather than "the beginning". ]
>> I'm personally more bothered by the fact that those #NNN use exactly the
>> same syntax as used with `print-circle` yet they don't have the
>> same semantics.
> The syntax isn't exactly the same (#N vs #N= and #N#) but annoyingly close.
Indeed, it's not as bad as I remembered.
> For that matter I would have preferred numbering the other way, starting at
> the bottom going up, like de Bruijn indices.
I love&hate de Bruijn indices as much as the next guy, but they're not
human-friendly (even more than the "like de Bruijn levels" we currently
use).
Stefan
next prev parent reply other threads:[~2022-05-14 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 11:32 bug#55395: What does (1 2 3 . #2) mean? Mattias Engdegård
2022-05-13 15:22 ` Lars Ingebrigtsen
2022-05-13 17:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-13 19:54 ` Lars Ingebrigtsen
2022-05-13 20:01 ` Mattias Engdegård
2022-05-14 13:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-05-18 14:29 ` Mattias Engdegård
2022-05-18 21:16 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 14:59 ` Mattias Engdegård
2022-05-13 16:08 ` Andreas Schwab
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=jwvpmkgfd88.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=55395@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.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).