From: Drew Adams <drew.adams@oracle.com>
To: 15824@debbugs.gnu.org
Subject: bug#15824: 24.3.50; `maphash`: document return value in doc string, just like in Elisp manual
Date: Wed, 6 Nov 2013 18:47:26 -0800 (PST) [thread overview]
Message-ID: <daa45416-4f26-4257-af8d-91f0ce9dd2c9@default> (raw)
Subject line says it all. Here is one place where this info might have
made things less confusing for one user:
http://stackoverflow.com/q/19826867/729907
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2013-10-19 on LEG570
Bzr revision: 114715 rgm@gnu.org-20131019023520-s8mwtib7xcx9e05w
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking 'CFLAGS=-O0 -g3' CPPFLAGS=-DGLYPH_DEBUG=1'
next reply other threads:[~2013-11-07 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 2:47 Drew Adams [this message]
2014-02-10 5:56 ` bug#15824: 24.3.50; `maphash`: document return value in doc string, just like in Elisp manual Lars Ingebrigtsen
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=daa45416-4f26-4257-af8d-91f0ce9dd2c9@default \
--to=drew.adams@oracle.com \
--cc=15824@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.
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).