emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Budiman Snowman <budimansnowman@gmail.com>,
	Samuel Loury <konubinix@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Annoyance when resolving clock idle time with emacsclient
Date: Fri, 09 Oct 2020 10:34:31 +0800	[thread overview]
Message-ID: <87k0w0m8js.fsf@localhost> (raw)
In-Reply-To: <CA+YqxJ50Pra-dr_pjm=xU9DFvyCpLs8dmCTDpsKc+fgTgm7Lag@mail.gmail.com>

> Thanks for the tip, I'll try pressing 10 times the next time it happens
> (which is probably today).

That sounds really odd. Could it be that there are multiple open
(without ending time) clocks existing in your org files?

Best,
Ihor

Budiman Snowman <budimansnowman@gmail.com> writes:

> On Thu, Oct 8, 2020 at 9:54 PM Samuel Loury <konubinix@gmail.com> wrote:
>
>> Hi,
>>
>> Actually, I realized though that even though the client was appearing
>> frozen, by pressing several times on "i" (ten times also), it eventually
>> closes the resolve clock stuff and let me play with emacs like nothing
>> happened. Then, I can run manually M-x org-resolve-clocks in case I
>> wanted to really resolve the clocks (using k or g or whathever).
>>
>> Even if this is an ugly workaround, I Hope that will help :-).
>>
>>
> Thanks for the tip, I'll try pressing 10 times the next time it happens
> (which is probably today).


  reply	other threads:[~2020-10-09  2:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 14:12 Annoyance when resolving clock idle time with emacsclient Budiman Snowman
2020-10-08 14:54 ` Samuel Loury
2020-10-08 15:30   ` Eric S Fraga
2020-10-09  1:09     ` Budiman Snowman
2020-10-09 11:40       ` Samuel Loury
2020-10-11 12:55         ` Budiman Snowman
2020-10-09  1:08   ` Budiman Snowman
2020-10-09  2:34     ` Ihor Radchenko [this message]
2020-10-09 11:42       ` Samuel Loury
2020-10-11 12:53       ` Budiman Snowman
2020-10-08 15:29 ` Eric S Fraga

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=87k0w0m8js.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=budimansnowman@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=konubinix@gmail.com \
    /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).