On 2026-06-27 08:45, Ihor Radchenko wrote: > Well. Its docstring says > > This applies to indirect buffers created with the commands > org-tree-to-indirect-buffer and org-agenda-tree-to-indirect-buffer. > > and says nothing about org-agenda-do-context-action.
I’m aware of what it says. ‘org-agenda-do-context’ action is a thin wrapper around ‘org-agenda-tree-to-indirect-buffer’; you might call that an implementation detail but I would disagree. I’m not interested in discussing this further. My point is just that it’s impolite to trample over user options. > I am looking at this again and wondering if a simple > org-with-wide-buffer would be more robust. POS may be within > narrowing, the containing heading could still be outside. In other words, just unconditionally widen? Sounds like more work, and I’m not sure what you’d gain, the macro is just: (save-excursion (save-restriction (widen) ,@body))) -- Jacob S. Gordon [email protected] Please don’t send me HTML emails or MS Office/Apple iWork documents. https://useplaintext.email/#etiquette https://www.fsf.org/campaigns/opendocument
