Annoyance when resolving clock idle time with emacsclient

Annoyance when resolving clock idle time with emacsclient

[Budiman Snowman]

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

I use emacsclient (with Konsole tabs, if that matters). I usually have
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. But often I cannot type a response in this buffer, or
in the original buffer's tab, so that I have to "killall emacsclient" and
reopen all the files/emacsclient instances.

Anyone experience the same?

[-- Attachment #2: Type: text/html, Size: 589 bytes --]

Re: Annoyance when resolving clock idle time with emacsclient

[Samuel Loury]

[-- 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 --]

Re: Annoyance when resolving clock idle time with emacsclient

[Eric S Fraga]

On Thursday,  8 Oct 2020 at 21:12, Budiman Snowman wrote:
> Anyone experience the same?

Yes, sporadically.  I use multiple tabs and multiple frames and
sometimes the prompt for the long idle clock is not visible...  I cannot
repeat it consistently, mind you.

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.4-38-g16f505

Re: Annoyance when resolving clock idle time with emacsclient

[Eric S Fraga]

On Thursday,  8 Oct 2020 at 16:54, Samuel Loury wrote:
> 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.

Similar with the 'q' key (usually requires 2-3 presses) although not
with 'k' (single press sufficient always).

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.4-38-g16f505

Re: Annoyance when resolving clock idle time with emacsclient

[Budiman Snowman]

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

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).

[-- Attachment #2: Type: text/html, Size: 968 bytes --]

Re: Annoyance when resolving clock idle time with emacsclient

[Budiman Snowman]

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

On Thu, Oct 8, 2020 at 10:30 PM Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> On Thursday,  8 Oct 2020 at 16:54, Samuel Loury wrote:
> > 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.
>
> Similar with the 'q' key (usually requires 2-3 presses) although not
> with 'k' (single press sufficient always).
>
>
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.

[-- Attachment #2: Type: text/html, Size: 992 bytes --]

Re: Annoyance when resolving clock idle time with emacsclient

[Ihor Radchenko]

> 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).

Re: Annoyance when resolving clock idle time with emacsclient

[Samuel Loury]

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

Budiman Snowman <budimansnowman@gmail.com> writes:

> On Thu, Oct 8, 2020 at 10:30 PM Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
>> On Thursday,  8 Oct 2020 at 16:54, Samuel Loury wrote:
>> > 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.
>>
>> Similar with the 'q' key (usually requires 2-3 presses) although not
>> with 'k' (single press sufficient always).
>>
>>
> 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
-- 
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 --]

Re: Annoyance when resolving clock idle time with emacsclient

[Samuel Loury]

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

Ihor Radchenko <yantar92@gmail.com> writes:

>> 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?

In my case, I am pretty sure to have only one clock open at most. The
clock report don't show any unfinished clock or any overlapping ones
and org-resolve-clock does not find any other unfinished clock other
than the one I am into.

-- 
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 --]

Re: Annoyance when resolving clock idle time with emacsclient

[Budiman Snowman]

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

On Fri, Oct 9, 2020 at 9:35 AM Ihor Radchenko <yantar92@gmail.com> wrote:

> > 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?
>
>
I never have multiple clocks active either, as I only have one "work
journal" file and only start one clock for the current day's entry.

Regards,

[-- Attachment #2: Type: text/html, Size: 830 bytes --]

Re: Annoyance when resolving clock idle time with emacsclient

[Budiman Snowman]

[-- 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 --]