Re: (org-element-parse-buffer) and (org-with-wide-buffer)

2023-01-11 Thread Ihor Radchenko
Michael Dauer writes: > Yes, but the missing headings are within the narrowed subtree. You are right. What is happening here is `org-element-parse-buffer' skipping over the folded heading: When VISIBLE-ONLY is non-nil, don't parse contents of hidden elements. -- Ihor Radchenko // yant

Re: (org-element-parse-buffer) and (org-with-wide-buffer)

2023-01-11 Thread Michael Dauer
Yes, but the missing headings are within the narrowed subtree. Am Mi., 11. Jan. 2023 um 12:22 Uhr schrieb Ihor Radchenko < yanta...@posteo.net>: > Michael Dauer writes: > > > But within (org-with-wide-buffer) the collapsed branches should be > visible. > > You have `org-narrow-to-subtree' inside

Re: (org-element-parse-buffer) and (org-with-wide-buffer)

2023-01-11 Thread Ihor Radchenko
Michael Dauer writes: > But within (org-with-wide-buffer) the collapsed branches should be visible. You have `org-narrow-to-subtree' inside `org-with-wide-buffer': 1. `org-with-wide-buffer' widens the buffer 2. `org-narrow-to-subtree' narrows it to subtree 3. `org-element-parse-buffer' gets exec

Re: (org-element-parse-buffer) and (org-with-wide-buffer)

2023-01-11 Thread Michael Dauer
But within (org-with-wide-buffer) the collapsed branches should be visible. Ihor Radchenko schrieb am Mi., 11. Jän. 2023, 11:02: > Michael Dauer writes: > > > 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

Re: (org-element-parse-buffer) and (org-with-wide-buffer)

2023-01-11 Thread Ihor Radchenko
Michael Dauer writes: > 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. This beha