Greg Troxel writes:
> (Thanks for fixing and your efforts on org. I've been an org user since
> at least July of 2010.)
>
> Just to be clear, is this the commit that needs applying to emacs
> sources, 29.3, 28.x, and so on?
Yes, that's the correct commit.
> It seems so, but I would rather not
(Thanks for fixing and your efforts on org. I've been an org user since
at least July of 2010.)
Just to be clear, is this the commit that needs applying to emacs
sources, 29.3, 28.x, and so on? It seems so, but I would rather not
guess. I'm asking on behalf of pkgsrc, where I am managing the re
Michaël Cadilhac writes:
> I have a task that was recurring, which I KILLED a few weeks ago. It
> now looks like:
>
> ** KILLED Do the right thing
>SCHEDULED: <2023-07-14 Fri +1w>
>
> ox-icalendar still exports it every week, because I have
> 'event-if-not-todo in org-icalendar-use-scheduled
emacs-orgm...@city17.xyz writes:
> Will a CVE be released?
Should be, I think.
If nobody reports it independently by tomorrow, I will look into how to
request a CVE number myself.
> ... I am interested if there are mitigating factors
> such as using `emacs -nw` (without GUI), thus no possible pr
Ihor Radchenko writes:
I just released Org mode 9.7.5 that fixes a critical vulnerability.
The release is coordinated with emergency Emacs 29.4 release.
Thanks for the release and the anouncement.
Will a CVE be released? I am interested if there are mitigating factors
such as using `emacs
Ihor Radchenko writes:
> Please upgrade your Org mode *and* Emacs ASAP.
*Org mode or Emacs.
The fix is purely in Org code, so upgrading Emacs is only needed when
you want to use built-in Org mode.
Otherwise, it is enough to upgrade Org mode via ELPA (the tarball will
be available soon, after E
I have a task that was recurring, which I KILLED a few weeks ago. It
now looks like:
** KILLED Do the right thing
SCHEDULED: <2023-07-14 Fri +1w>
ox-icalendar still exports it every week, because I have
'event-if-not-todo in org-icalendar-use-scheduled (which is the
behavior I want for some o
Dear all,
I just released Org mode 9.7.5 that fixes a critical vulnerability.
The release is coordinated with emergency Emacs 29.4 release.
Please upgrade your Org mode *and* Emacs ASAP.
The vulnerability involves arbitrary Shell code evaluation when
previewing attachments in Emacs MUA (gnus-bas
Hello!
I noticed that in the function org-babel-merge-params the arguments are
alists rather than plists.
To this end, I created a patch that updates the relevant variable names as
well as the docstring (see attachment).
From db9d5b77aedfb87aa0a3382f6be9d5921eef2ffd Mon Sep 17 00:00:00 2001
From:
Max Nikulin writes:
>> If you can, please do not make such assertions without testing.
>
> I am sorry, I had no intention to offend you. I missed that the removed
> line with explicit list of punctuation characters was commented out. I
> have tried the regexp used before (a part of v6.34)
>
Nathan Nichols writes:
>> This looks like a copy-paste of `org-element-normalize-string'.
>> Why not simply calling `org-element-normalize-string'?
>
> I changed it at one point, but then changed it back and didn't realize that
> it was ultimately unchanged.
> Here's a patch that uses `org-elemen
It was a long discussion this time (almost 3 hours).
We ended up talking in-depth about Org mode development and some very
technical aspects of it.
- As usual, we started from posting Sacha's News, but with a bit of a twist
- Since recently, https://orgmode.org shows Org mode-related news on t
Ihor Radchenko writes:
> Vidianos Giannitsis writes:
>
>> I got this error while working on an org file. It appears to be
>> something related to org-fragtog, or the creation of the latex
>> preview. Its the first time I see it and I am not sure how it happened
>> (can't reproduce it), but the e
13 matches
Mail list logo
