Ihor Radchenko writes:
> May you try the attached patch?
This fixes the issue, thanks Ihor! I do wonder why this workaround is necessary:
do you have an idea what changed in Emacs 30 that introduced this bug?
Best,
Rens
Hello,
Currently =org-clock-string-limit= truncates rather crudely. It just does a
=substring=, which results in the closing parenthesis of the clock string
getting cut off. The attached patch seeks to improve this truncation behavior
by trimming the headline such that the closing paren can be dis
Rens Oliemans writes:
> Ihor Radchenko writes:
>
>> May you try the attached patch?
>
> This fixes the issue, thanks Ihor!
Applied, onto main.
Fixed.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=cd4cb4552a
> ...I do wonder why this workaround is necessary:
> do you have an i
Karthik Chikmagalur writes:
>> What if you try the attached diff?
>
> Two cases, profiles for both are attached:
>
> 1. When running `save-buffers-kill-emacs', the time is down from several
> minutes to about 10 seconds -- still undesirably long but not egregious.
> This is the profile org-persis
[Adding Org mailing list back to the loop]
Doug Harris writes:
> (sending this to just you - if you have advice on how best to share
> multiple files with the orgmode list, I can send there as well)
Small files can simply be attached.
We only avoid large files on the list (those are usually sha
> Would you consider it? See
> https://orgmode.org/worg/org-contribute.html#copyright
I have already done the copyright assignment.
> Please add a proper commit message, if you can.
> We also need an ORG-NEWS entry announcing the new customization.
> "carefully set craft regexp..." reads as if Or
Lei Zhe writes:
> I realized that it's challenging to handle the error properly if the
> return value of org-babel-tangle-single-block remains unchanged.
>
> Consider your code block:
> #+begin_src emacs-lisp :tangle '("1.el" "2.el")
> (+ 1 2)
> #+end_src
>
> In the org-babel-tangle--unbracke
>> you can simply return multiple (file-name src-lang start-line file link
>> source-name params body comment) items.
>> (file-name1 ... link1 ...)
>> (file-name2 ... link2 ...)
I don't get it, shouldn't it be as shown below? Then the returned
results got changed.
((file-name1 ... link1 ...)
(fi
Ihor Radchenko writes:
> Björn Bidar writes:
>
>> +*** =org-link-gnus= Ensure that other frame is alive before selecting it
>> +Ensure that the Gnus frame is alive before selecting it if it was
>> +activated before. If a Gnus frame existed before call it using
>> +~gnus-other-frame~. Using the
