emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Michael Dauer <mick.dauer@gmail.com>
To: emacs-orgmode@gnu.org
Subject: (org-element-parse-buffer) and (org-with-wide-buffer)
Date: Wed, 11 Jan 2023 10:47:48 +0100	[thread overview]
Message-ID: <CAP7OBxJgOgsWJ6T0QVh5=Hcq6CpoY2Kg114VZKTig-P9BmQECQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

I see a potential bug here: (org-element-parse-buffer) with VISIBLE-ONLY
does not include regions made visible with (org-with-wide-buffer).

Test (Have h2.2.1 collapsed before running it.):
>>>
* h1
** h2
*** h2.1
*** h2.2
#+begin_src elisp
(org-with-wide-buffer
 (org-narrow-to-subtree)
 (goto-char (point-min))
 (list
  (--map (cadr it)
         (s-match-strings-all "^\\*+ \\(.*\\)$"
                              (buffer-substring-no-properties
                               (point-min) (point-max))))
  (org-element-map (caddr (org-element-parse-buffer 'object t)) 'headline
    (lambda (it) (org-element-property :raw-value it))))
)
#+end_src

#+RESULTS:
| h2.2 | h2.2.1 | h2.2.1.1 |
| h2.2 | h2.2.1 |          |

**** h2.2.1
***** h2.2.1.1
aaaaa
*** h2.3
* h3
<<<

I would expect both output rows to be identical. But it seems
that (org-with-wide-buffer) has no effect on (org-element-parse-buffer)
with VISIBLE-ONLY argument.

While I believe this is a bug, I would also appreciate hearing about
possible work-arounds.

thx

[-- Attachment #2: Type: text/html, Size: 1351 bytes --]

next             reply	other threads:[~2023-01-11  9:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11  9:47 Michael Dauer [this message]
2023-01-11 10:03 ` (org-element-parse-buffer) and (org-with-wide-buffer) Ihor Radchenko
2023-01-11 11:19   ` Michael Dauer
2023-01-11 11:23     ` Ihor Radchenko
2023-01-11 11:56       ` Michael Dauer
2023-01-11 12:02         ` 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:
  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='CAP7OBxJgOgsWJ6T0QVh5=Hcq6CpoY2Kg114VZKTig-P9BmQECQ@mail.gmail.com' \
    --to=mick.dauer@gmail.com \
    --cc=emacs-orgmode@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

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