unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55562-done@debbugs.gnu.org, dancol@dancol.org, monnier@iro.umontreal.ca
Subject: bug#55562: 28.1.50; Wrong hash table return values in Elisp manual
Date: Tue, 28 Jun 2022 10:06:46 +0300	[thread overview]
Message-ID: <87h745i7w9.fsf@tcd.ie> (raw)
In-Reply-To: <83wnd17bw2.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 27 Jun 2022 22:35:56 -0400")

found 55562 24.1
close 55562 28.2
quit

Eli Zaretskii [2022-06-27 22:35 -0400] wrote:

>> From: "Basil L. Contovounesios" <contovob@tcd.ie>
>> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  Daniel Colascione
>>  <dancol@dancol.org>,  55562@debbugs.gnu.org
>> Date: Mon, 27 Jun 2022 23:43:59 +0300
>> 
>> Is this suitable for Emacs 28?
>
> If the behavior is the same there, yes.

The puthash behaviour has been with us since Emacs 22, and the clrhash
behaviour since Emacs 24, it's just the Elisp manual that was never
updated accordingly.

So I've now updated the manual in emacs-28, and I'm closing this report.

Fix hash table function return values in manual
091b22cb12 2022-06-28 10:03:53 +0300
https://git.sv.gnu.org/cgit/emacs.git/commit/?id=091b22cb12

Thanks,

-- 
Basil





      reply	other threads:[~2022-06-28  7:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21 20:29 bug#55562: 28.1.50; Wrong hash table return values in Elisp manual Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-22  5:10 ` Eli Zaretskii
2022-06-27 20:43   ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-28  2:35     ` Eli Zaretskii
2022-06-28  7:06       ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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=87h745i7w9.fsf@tcd.ie \
    --to=bug-gnu-emacs@gnu.org \
    --cc=55562-done@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=dancol@dancol.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).