From: Marcin Borkowski <mbork@mbork.pl>
To: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: New Org (from main) and slow clocking
Date: Fri, 17 Feb 2023 08:03:37 +0100 [thread overview]
Message-ID: <87cz68epti.fsf@mbork.pl> (raw)
In-Reply-To: <87sff4bx8k.fsf@mbork.pl>
On 2023-02-17, at 07:51, Marcin Borkowski <mbork@mbork.pl> wrote:
> Hi all,
>
> I have just updated my Org (from the main branch, Org mode version
> 9.6.1, release_9.6.1-253-g74eb0f), and I noticed an issue with clocking.
> I have an "ongoing" task which already accumulated 7000+ clock entries,
> and clocking in takes close to 90 seconds. It was instantaneous before
> (version 9.6-pre, release_9.5.5-853-g7b9d8e). What can I do now?
>
> And how can I downgrade? (I tried the "logical" thing, i.e., I checked
> out a "tmp" branch at tag release_9.6.1 and ran "make update", but it
> didn't work because it (obviously) couldn't pull the "tmp" branch.
Ok, so I think I managed to downgrade (make cleanall, make, sudo make
install - is that correct?), but the problem persists in 9.6.1...
> Alternatively, since Org mode is much more mature now than a few years
> ago, how can I get rid of my Git-based installation in favor of the Elpa
> package (which, I assume, should be much more stable/bug-free)? (I
> understand that by using bleeding edge Org mode I risk a bit, and maybe
> it's time to trade new/shiny for safe...)
Best,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2023-02-17 7:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 6:51 New Org (from main) and slow clocking Marcin Borkowski
2023-02-17 7:03 ` Marcin Borkowski [this message]
2023-02-17 12:02 ` Ihor Radchenko
2023-02-17 13:23 ` Marcin Borkowski
2023-02-17 13:32 ` Ihor Radchenko
2023-02-17 16:46 ` Marcin Borkowski
2023-02-17 18:14 ` Ihor Radchenko
2023-02-17 19:40 ` Marcin Borkowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cz68epti.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).