Re: [BUG] Resolving idle clocks needs multiple keystrokes [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

2022-10-15 Thread Ihor Radchenko
Ignacio Casso writes: >> So the problem is in (org-user-idle-seconds), which in my window system >> boils down to a call to (current-idle-time). It should return 0 after >> answering the prompt, but in my system it keeps counting up. At this >> point I stopped investigating since that function

Re: [BUG] Resolving idle clocks needs multiple keystrokes [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

2022-03-20 Thread Roméo La Spina
Thanks for your answer! I will do that as soon as I have a little more time. Ignacio Casso writes: >> Hmm, I see the problem. I didn't think about that. >> Thank you very much for your suggestion. But what about using >> read-char-exclusive? It seems to have a timeout argument too, and >>

Re: [BUG] Resolving idle clocks needs multiple keystrokes [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

2022-03-20 Thread Ignacio Casso
> Hmm, I see the problem. I didn't think about that. > Thank you very much for your suggestion. But what about using > read-char-exclusive? It seems to have a timeout argument too, and > should apparently fix the issue (ie. the prompt will no longer > disappear at the first unintentional click).

Re: [BUG] Resolving idle clocks needs multiple keystrokes [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

2022-03-19 Thread Roméo La Spina
Hmm, I see the problem. I didn't think about that. Thank you very much for your suggestion. But what about using read-char-exclusive? It seems to have a timeout argument too, and should apparently fix the issue (ie. the prompt will no longer disappear at the first unintentional click). Romeo

Re: [BUG] Resolving idle clocks needs multiple keystrokes [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

2022-03-19 Thread Ignacio Casso
> Hi, > > I don't know how closely it is related to your problem, but I've > reported another issue revolving around the use of read-char for the > prompt to resolve clocks. See > [[https://lists.gnu.org/archive/html/emacs-orgmode/2022-02/msg00278.html]]. > > Unfortunately I an not advanced

Re: [BUG] Resolving idle clocks needs multiple keystrokes [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

2022-03-19 Thread Roméo La Spina
Hi, I don't know how closely it is related to your problem, but I've reported another issue revolving around the use of read-char for the prompt to resolve clocks. See [[https://lists.gnu.org/archive/html/emacs-orgmode/2022-02/msg00278.html]]. Unfortunately I an not advanced enough in Elisp to

Re: [BUG] Resolving idle clocks needs multiple keystrokes [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

2022-03-13 Thread Ignacio Casso
> So the problem is in (org-user-idle-seconds), which in my window system > boils down to a call to (current-idle-time). It should return 0 after > answering the prompt, but in my system it keeps counting up. At this > point I stopped investigating since that function is defined in C. > I have