Sebb

Here are some plugins that reference _content: https://github.com/getpelican/pelican-plugins/blob/c61bd12914fd52af1808c53151a07225e7c3341c/glossary/glossary.py#L36 https://github.com/getpelican/pelican-plugins/blob/c61bd12914fd52af1808c53151a07225e7c3341c/section_number/section_number.py#L78 https://github.com/pelican-plugins/photos/blob/24fbe6cf79e2c25eead3361d1a29dbf14a77bf39/pelican/plugins/photos/photos.py#L1839

Your suggested change does solve the issue. It does not change the line where `_content` is referenced: `soup = bs4.BeautifulSoup(content._content, 'html.parser')`

We are going round in circles. ._content and .content don't always return the same value, otherwise plugins would not need to use _content.

The current output from help would need augmenting, as it does not give full details of all the options. For example it would be useful to document how to override...

Note: the simplification only really works for mboxo format mailboxes. A different approach would be needed to support mboxrd format as this can have an arbitrary number of '>' chars...

AFAICT, we do allow CORS [1] on hosts served by the tlp-server: ``` $ curl -sSIL https://infra.apache.org HTTP/2 200 server: Apache last-modified: Thu, 27 Feb 2025 19:43:43 GMT etag: "3ec6-62f24e85582e8"...

FTR the mboxo format is not supported by Python email on input, see #212

I learnt of the tool via this issue: https://issues.apache.org/jira/browse/INFRA-26638?focusedCommentId=17936653&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17936653

Yes, but all 3 appear in the actions list, and if one fails, it is not obvious which has failed without further investigation.

I was referring to the list of workflows here: https://github.com/r-lib/actions/actions