Bug: Incorrect done TODO keywords highlighting in column view

Hi, In columns view, all TODO keywords except those with face set explicitly with org-todo- keyword-faces are red. Done keywords should be green. Patch below. BR, Martin >From a4df0da1057afbe90ea0e457158082b15386a164 Mon Sep 17 00:00:00 2001 From: Martin Kampas Date: Fri, 9 Oct 2020 07:43:17

Re: yank in middle of text a headline

> thanks for trying it. i am using 9.4. perhaps one of my settings has > a different interpretation from 9.3? if that's not hte issue then Can you reproduce with emacs -Q? Samuel Wales writes: > thanks for trying it. i am using 9.4. perhaps one of my settings has > a different

Re: Annoyance when resolving clock idle time with emacsclient

> 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

Re: Disambiguate internal links?

On Fri, Sep 4, 2020 at 9:47 PM Bastien wrote: > Hi Budiman, > > Budiman Snowman writes: > > > One way I know is using a unique dedicated target, e.g.: > > > > * topic1 > > See topic [[topic2]]. > > See glossary [[glossary topic2][topic2]]. > > > > * topic2 > > * glossary > > ** <> topic1 > > **

Re: Annoyance when resolving clock idle time with emacsclient

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

Re: Annoyance when resolving clock idle time with emacsclient

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,

Re: yank in middle of text a headline

thanks for trying it. i am using 9.4. perhaps one of my settings has a different interpretation from 9.3? if that's not hte issue then On 10/4/20, Ihor Radchenko wrote: >> if i copy x and yank it where | is, it yanks immediately above y. i >> prefer that it yanks at |. is this possible? >

Re: Annoyance when resolving clock idle time with emacsclient

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,

Re: Annoyance when resolving clock idle time with emacsclient

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'

Re: Annoyance when resolving clock idle time with emacsclient

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

Annoyance when resolving clock idle time with emacsclient

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