From: Budiman Snowman <budimansnowman@gmail.com>
To: Samuel Loury <konubinix@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Annoyance when resolving clock idle time with emacsclient
Date: Sun, 11 Oct 2020 19:55:04 +0700 [thread overview]
Message-ID: <CA+YqxJ7-2Bn+NTEHMc=M8gW8hVwz-fB8Arei=2RNhqxPjtCW1Q@mail.gmail.com> (raw)
In-Reply-To: <87a6wvhbke.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
On Fri, Oct 9, 2020 at 6:40 PM Samuel Loury <konubinix@gmail.com> wrote:
> > I almost always choose 'k' (keep) and it is often not responding after
> the
> > first or several presses. But as Samuel Loury pointed out, I'll try
> > pressing ten times at least, the next time it happens.
>
> IIRC, pressing 'k', even a lot, did not work. I realized that i might be
> linked to the fact that 'k' asks for some minibuffer input and this
> input is waited in the other frame. And when emacs is waiting for some
> minibuffer input in one frame, there is nothing I could do to get the
> control on the other frame.¹
>
> What I am suggesting is to press a lot 'i', until org-mode releases its
> grasp on the other frame. You notice that it is so when the letter 'i'
> gets written in front of you :-). Then, when org-mode let you go, you
> can run M-x org-resolve-clocks and you will be able to press 'k' this
> time.
>
> I hope this is clearer this time.
>
> Good luck :-).
>
> ¹ Actually, there is one way. Send the SIGUSR2 signal to emacs (pkill
> -SIGUSR2 emacs) so that it starts the debugger (in your current focused
> frame), then close the debugger and re run manually M-x
> org-resolve-clocks. SIGUSR2 would have enabled the debug-on-quit, so
> disable it with M-x toggle-debug-on-quit
>
>
Ah, got it. Will also try the SIGUSR2 trick, thanks.
Regards,
[-- Attachment #2: Type: text/html, Size: 1791 bytes --]
next prev parent reply other threads:[~2020-10-11 12:55 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 [this message]
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='CA+YqxJ7-2Bn+NTEHMc=M8gW8hVwz-fB8Arei=2RNhqxPjtCW1Q@mail.gmail.com' \
--to=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).