emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Phil Hudson <phil.hudson@iname.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs orgmode-mailinglist <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Re: [BUG] org-element-map doco should refer to org-element-parse-buffer [9.5.2 (9.5.2-gfbff08 @ /home/phil/.emacs.d/elpa/org-9.5.2/)]
Date: Tue, 3 May 2022 09:10:43 +0100	[thread overview]
Message-ID: <CAJ1MqVEr8+gdPciETc2tGCgigGjpTAj7gZx9PhTbXZZ8n+_gpg@mail.gmail.com> (raw)
In-Reply-To: <87ee1bgu06.fsf@localhost>

Thanks Ihor, that's great!

One tiny nit-pick: I think "e.g." is deprecated in favor of the
explicit literal "for example". My source for this is (info "(elisp)
Documentation Tips").

Also, just spotted what I think is a pre-existing typo, "objects
types", which I think should probably be just "object types". Might as
well fix that while we're at it.

Best,
Phil

On Tue, 3 May 2022 at 04:43, Ihor Radchenko <yantar92@gmail.com> wrote:
>
> Phil Hudson <phil.hudson@iname.com> writes:
>
> > The documentation for function `org-element-parse-buffer' helpfully
> > directs the user to that of function `org-element-map', but the
> > documentation for the latter makes no mention of
> > `org-element-parse-buffer'. It contains lengthy and helpful explanations
> > of what to do with its `data' parameter, but no hint as to how to obtain
> > that data.
>
> Sounds reasonable.
> Will something like the attached do?
>
> Best,
> Ihor
>


  reply	other threads:[~2022-05-03  8:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30  6:12 [BUG] org-element-map doco should refer to org-element-parse-buffer [9.5.2 (9.5.2-gfbff08 @ /home/phil/.emacs.d/elpa/org-9.5.2/)] Phil Hudson
2022-05-03  3:44 ` [PATCH] " Ihor Radchenko
2022-05-03  8:10   ` Phil Hudson [this message]
2022-05-14  5:09     ` Ihor Radchenko
2022-05-14  8:01       ` Phil Hudson

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.orgmode.org/

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

  git send-email \
    --in-reply-to=CAJ1MqVEr8+gdPciETc2tGCgigGjpTAj7gZx9PhTbXZZ8n+_gpg@mail.gmail.com \
    --to=phil.hudson@iname.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    /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/org-mode.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).