From: "���п� via Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: "32841" <32841@debbugs.gnu.org>
Subject: bug#32841: assoc-set fails with dot notation association list
Date: Tue, 22 Oct 2024 11:48:53 +0800 [thread overview]
Message-ID: <tencent_1C2635904F28049C0C963CB9@qq.com> (raw)
In-Reply-To: <d61a791aaa734245ac705bb5196ff18e@gtri.gatech.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 642 bytes --]
The thread and all replies were in 2018. Six years later, in 2024, Anyone opening the up-to-date online manual still sees the old bad code there! The manual is not adjusted even though previous emails had pointed the cause and solution out!
Could anyone take action to edit api-data.texi in guile's git savannah repo by replacing the bad code in @node Alist Example to a good one, using list and cons instead of directly quoting?
ÉîÛÚ´óѧ
³ÂÓп¥
[-- Attachment #2: Type: text/html, Size: 4681 bytes --]
next prev parent reply other threads:[~2024-10-22 3:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 20:33 bug#32841: assoc-set fails with dot notation association list Hood, Christopher L.
2018-09-25 22:04 ` John Cowan
2018-09-27 3:02 ` Mark H Weaver
2018-09-27 12:09 ` John Cowan
2024-10-21 8:54 ` ���п� via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2024-10-21 20:26 ` Tomas Volf
2024-10-22 3:48 ` ���п� via Bug reports for GUILE, GNU's Ubiquitous Extension Language [this message]
2024-10-22 17:51 ` lloda
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tencent_1C2635904F28049C0C963CB9@qq.com \
--to=bug-guile@gnu.org \
--cc=2024110144@mails.szu.edu.cn \
--cc=32841@debbugs.gnu.org \
/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.
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).