Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Ihor Radchenko writes:
> Maske writes:
>
>> There are some links, that I am afraid don't work:
>> ...
>> ‘constants.el’ by Carsten Dominik [...]
>> http://www.astro.uva.nl/~dominik/Tools.
>>
>>
>> # That link is dead. Maybe this would be the correct one:
>>
Hi all,
It appears that Emacs 27 lacks the optional argument for
`get-buffer-create`, while `org-element-parse-secondary-string`
relies on it. This problem was introduced by the commit 37d6bde27fe2.
Additionally, `org-id-find-id-in-file` also uses `get-buffer-create`
with a second argument, but
Ihor Radchenko writes:
>> 1. In addition to printing `org-babel-python-eoe-indicator' after
>>execution, we could also print out a "beginning of execution"
>>indicator before execution, and then capture the output between the
>>beginning and end indicators. This is how the async
Ihor Radchenko writes:
> We have fairly regular CI test failures for one of the ob-python tests.
> The test does not fail _every_ time, but I keep seeing the problem in
> various Emacs versions, including Emacs 29.
>
> Example log: https://builds.sr.ht/~bzg/job/1047678#task-build
>
> In the test
Maske writes:
> From the first day, I liked org-num-mode, but I think that its default
> which numbers all headlines could be problematic.
>
> Right now it only has the options to exclude headlines from being
> numbered, so it could be necessary to modify a big amount of headlines,
> for
Hi
From the first day, I liked org-num-mode, but I think that its default
which numbers all headlines could be problematic.
Right now it only has the options to exclude headlines from being
numbered, so it could be necessary to modify a big amount of headlines,
for numbering just a tree.
No, no, not clock check mode.
- I created a TODO with a scheduled time that repeats. When completed
it remains alive to be scheduled the next day.
- I started the clock on that TODO task.
- Then completed the task with 't' in the Agenda view.
- The task's "clock time" shows in the log ...
Ihor Radchenko writes:
> You may instead introduce a new allowed value for
> `org-hide-emphasis-markers' to hide markers for non-nil entries in
> `org-emphasis-alist'. Maybe even allow the value to be an explicit list
> of the markers to be hidden '("*" "_" ...).
One month have passed since the
Daniel Ortmann writes:
> In the last entry below, the "Clocked:" part of the log would have
> showed 3:47 (i.e. the current local CDT time) rather than the time to
> complete the task which is now correctly shown as 0:01 minutes.
Do you mean that you used agenda clockcheck mode? I tried and I
Hey,
The problem no longer appears! Excellent. Not sure what fixed it.
In the last entry below, the "Clocked:" part of the log would have
showed 3:47 (i.e. the current local CDT time) rather than the time to
complete the task which is now correctly shown as 0:01 minutes.
Problem fixed ...
Daniel Ortmann writes:
> I have a repeatedly-scheduled TODO with this entry for the schedule:
> SCHEDULED: <2023-10-15 Sun .+1d -0d>
>
> The TODO is marked with 'sometag'.
>
> In the regular agenda view (C-a a) I narrow with /sometag.
> Then S-I to start the clock.
> Finally, t and C-c C-c to
Elias Kueny writes:
> I found an issue with fish shell code blocks, in that the `:var' parameter
> generates a command that is not syntaxically correct. Fish uses `set variable
> value' instead of `variable = value'. As a result, org-babel throws an error
> when executing the code block. This
Vladimir Nikishkin writes:
> For some time I have been wondering why auto-clockout does not use
> x11idle on my machine.
> ...
> or, even better:
>
> #+begin_src elisp
> (defun org-clock-auto-clockout-maybe ()
>(if (< org-clock-auto-clockout-timer (if org-x11idle-exists-p
>
YE writes:
>> Ihor Radchenko writes:
>> See the attached tentative patch.
>
> Thanks, LGTM so far.
Applied, onto bugfix.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=51937d4b1
Fixed.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at
15 matches
Mail list logo