On Fri, Oct 9, 2020 at 6:40 PM Samuel Loury 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
On Fri, Oct 9, 2020 at 9:35 AM Ihor Radchenko 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
Ihor Radchenko 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
Budiman Snowman writes:
> On Thu, Oct 8, 2020 at 10:30 PM Eric S Fraga 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
>> >
> 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 writes:
> On Thu, Oct 8, 2020 at 9:54 PM
On Thu, Oct 8, 2020 at 10:30 PM Eric S Fraga 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
On Thu, Oct 8, 2020 at 9:54 PM Samuel Loury 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,
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,
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'
Hi,
Budiman Snowman 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
10 matches
Mail list logo
