Hello,
I think that even when ":eval no" is set, eval should happen if the user
explicitly requests it.
The use case is that I have code that takes an unreasonable amount of compute
time to run it in Emacs (e.g. a full day of compute time). I think even with
:async this type of code should be
i don't use the priority stuff, but i think it could perhaps be useful
to use terminology to distinguish the priority stuff from
the priority stuff.
i.e.
1] the stuff i don't use that you are talking about
2] [#A] and all that
when i was a beginner i got confused by that.
:)
On 10/9/19, Adam
Hi Anton, Nicolas, et al,
I'm in favor of tidying up the priority-related code, as I also have
found it hard to follow.
But please do not change the API of these functions, i.e. the signatures
and return values. Their output is used in other packages, including
some of mine like org-rifle, org-s
I just upgraded to MacOS 10.15 and am experiencing some pain.
The faithful org-download-screenshot from
https://github.com/abo-abo/org-download stopped working.
Instead of capturing a window or selection, it just copied the background.
This - forbidding screen capture - is considered a security
