My takeaways from a conversation with Ihor
- Well, Org's own automatic cache (`org-element-cache-persistent`) is sparse,
so it will not be useful directly.
- But the output of running `(org-element-parse-buffer)` in a given file could
be written somewhere, via org-persist perhaps, and then I co
Dear All,
I've just merged a pull request which hopefully fixes the problem
(commit e3bf1f8).
(Incidentally, the problems came from major changes in how libxml2
parses trivial html fragments.)
best wishes,
András
On Thu, 22 May 2025 at 22:11, András Simonyi wrote:
>
> Dear All,
>
> thanks for rep
Matteo Valsasina writes:
CAPTURE TEMPLATE FOR ORG:
("m" "TODO from Mail" entry (file+headline "~/org_todo/notes.org" "Mail Tasks")
"* TODO %? %a\nSCHEDULED: %t
:PROPERTIES:
:CREATED: %U
:END:
:LOGBOOK:"
:prepend t :empty-lines 1)
Thank you Matteo for this tem
David Masterson writes:
>> The starting place is `org-compile-file'. Its LOG-BUF argument defines
>> where the compilation output is dumped. You can augment that output
>> with some information about which file is being compiled and using
>> which commands.
>
> Hmm. Am I right in assuming LOG-BU
Pedro Andres Aranda Gutierrez writes:
>> 1. We introduce org-latex-fontsets variable that will hold pre-defined
>>set of fonts that we ship with Org mode.
>
> I see a small disadvantage in defining font sets in a generalised way,
> which I'm experiencing in my multi-OS and which was pointed o
Pedro Andres Aranda Gutierrez writes:
> A really cool page for people with some experience in Emacs. Lots of cool
> ideas I need to look at.
> The only downside is the "some experience". What about people who are
> starting?
Sorry, I need to clarify why I shared the link.
The specific section of
