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.
--
Inside org-babel code blocks, emacs matches parens incorrectly whenever
different bracket types (eg <> {} []) are used.
For example the following in an .org file will cause check-parens to throw
an error:
#+BEGIN_SRC emacs-lisp
(> 1 0)
#+END_SRC
Where in an .el it will interpret the parens c
Hi Bhavin,
Thanks for your prompt response.
I have followed those steps and that is the same behaviour I get.
The expected behaviour is for it to clock out of the subtree, instead of
giving the "Clock start time is gone" error.
Regards,
- Eddie Drury
On Wed, 21 Jul 2021 at 02:
subheading. If I refile this subheading and then run org-clock-out, I get
the error "Clock start time is gone".
When not working in an indirect buffer, Org Mode is able to track this
subtree and clock out of it, which is the expected behaviour.
Thanks in advance.
Regards,
- Eddie Drury
,
- Eddie Drury
Emacs : GNU Emacs 26.3 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.14)
of 2020-03-26, modified by Debian
Package: Org mode version 9.5 (nil @
/home/eddie/.emacs.d/.local/straight/build-26.3/org-mode
