emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Loury <konubinix@gmail.com>
To: Budiman Snowman <budimansnowman@gmail.com>,
	Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Annoyance when resolving clock idle time with emacsclient
Date: Thu, 08 Oct 2020 16:54:51 +0200	[thread overview]
Message-ID: <87k0w0wyx0.fsf@gmail.com> (raw)
In-Reply-To: <CA+YqxJ7MWkjXFNXG19ewX+gKtZZq-rzmvB0Z7hCyY5DoatdEhg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]

Hi,

Budiman Snowman <budimansnowman@gmail.com> writes:

> several  emacsclient instances open in different tabs. When I start a clock
> and then get away long enough, Emacs will prompt me to resolve the idle
> time in different buffer that has the clock, usually in the first buffer
> that I get back to.
[...]

> Anyone experience the same?

I do :-).

I generally open emacs in my graphical session and when I am AFK, I
connect using ssh in termux on my computer and play with emacs via an
emacsclient in the terminal.

Also, another boring behavior of org-resolve-clocks is that I generally
have to press several times (about ten times) on the "i" key to ignore
the message.

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 :-).
-- 
Konubinix
GPG Key    : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-10-08 14:56 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 [this message]
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
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=87k0w0wyx0.fsf@gmail.com \
    --to=konubinix@gmail.com \
    --cc=budimansnowman@gmail.com \
    --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).