Sure, please check out the patch.

BTW, do we need to document the change in org-manual.org?

Lei Zhe

On Sun, Mar 29, 2026 at 11:12 PM Ihor Radchenko <[email protected]> wrote:
>
> Lei Zhe <[email protected]> writes:
>
> >>For archiving, I can see how this may depend on user taste.
> >>Could you please provide more details about your workflow? Do you really
> >>need archived subtrees?
> > Yes, in my workflow I do rely on archived subtrees.
> >
> > I maintain an accounting Org file that generates yearly journal files.
> > After closing a fiscal year, I archive the corresponding headline.
> > However, the ledger entries under that archived headline still need to
> > be tangled, just like the current year's entries.
> > ...
> > Because this may ultimately be a matter of user preference, making the
> > treatment of archived subtrees configurable (for example, via a
> > defcustom) would allow users like me to adapt the behavior to their
> > workflow without altering the current default for others.
>
> Sorry for the late reply.
>
> +1
> defcustom would make sense.
> Similar to how there is `org-export-with-archived-trees'.
>
> --
> Ihor Radchenko // yantar92,
> Org mode maintainer,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>

Attachment: 0001-ob-tangle-Make-tangling-from-archived-trees-optional.patch
Description: Binary data

Reply via email to