emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marco Wahl <marcowahlsoft@gmail.com>
To: Ignacio Casso <ignaciocasso@hotmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Typo in manual [9.5.2 (9.5.2-gfbff08 @ /home/ignacio/.emacs.d/elpa/org-9.5.2/)]
Date: Thu, 10 Feb 2022 11:59:15 +0100	[thread overview]
Message-ID: <874k57c7i4.fsf@gmail.com> (raw)
In-Reply-To: <PAXPR06MB7760636DC6C66FB22B27E692C62F9@PAXPR06MB7760.eurprd06.prod.outlook.com> (Ignacio Casso's message of "Thu, 10 Feb 2022 11:01:28 +0100")

Ignacio Casso <ignaciocasso@hotmail.com> writes:

> I would like to report a minor typo in the manual, although I'm not sure
> if this is the right place (please point me to it if it's not).


And this is the right place to report this bug.  Thanks!

> In the section Appendix A Hacking -> Using the Mapping API
> (https://orgmode.org/manual/Using-the-Mapping-API.html), it says that
> org-map-entries returns an alist, but it actually returns a list (as
> correctly stated by C-h f org-map-entries).

To me this looks like the documentation in the manual started from the
documentation of the function.  and with time these two documentations

What about removing the (diverged) duplication of the documentation of
function org-map-entries from the manual?

  reply	other threads:[~2022-02-10 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 10:01 [BUG] Typo in manual [9.5.2 (9.5.2-gfbff08 @ /home/ignacio/.emacs.d/elpa/org-9.5.2/)] Ignacio Casso
2022-02-10 10:59 ` Marco Wahl [this message]
2022-10-06 11:35   ` [HELP] Please help checking function definitions in the manual vs. docstrings (was: [BUG] Typo in manual [9.5.2 (9.5.2-gfbff08 @ /home/ignacio/.emacs.d/elpa/org-9.5.2/)]) Ihor Radchenko

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874k57c7i4.fsf@gmail.com \
    --to=marcowahlsoft@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ignaciocasso@hotmail.com \


* 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


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).