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 +0200
Subject: [PATCH] org-colview: Fix done TODO keywords highlighting
* lisp/org-colview.el (org-columns--overlay-text): Populate
org-done-keywords from org-done-keywords-for-agenda or the done keywords
will use the same face as not-done keywords.
---
lisp/org-colview.el | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/lisp/org-colview.el b/lisp/org-colview.el
index e50a4d7c8..827f57e5e 100644
--- a/lisp/org-colview.el
+++ b/lisp/org-colview.el
@@ -365,7 +365,9 @@ ORIGINAL is the real string, i.e., before it is modified by
org-tags-special-faces-re
(lambda (m) (propertize m 'face (org-get-tag-face m)))
v nil nil 1)))
- ("TODO" (propertize v 'face (org-get-todo-face original)))
+ ("TODO"
+ (let ((org-done-keywords org-done-keywords-for-agenda))
+ (propertize v 'face (org-get-todo-face original
(_ v)
(defvar org-columns-header-line-remap nil
--
2.28.0
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 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? >> >> I cannot reproduce it on my side. What is the org-mode version you are >> using? >> >> Best, >> Ihor >> >> Samuel Wales writes: >> >>> === >>> * x >>> hi >>> | >>> there >>> * y >>> === >>> >>> if i copy x and yank it where | is, it yanks immediately above y. i >>> prefer that it yanks at |. is this possible? >>> >>> is this new behavior? >> > > > -- > The Kafka Pandemic > > Please learn what misopathy is. > https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
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 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, 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: 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 > > ** <> topic2 > > > > What are other ways available? > > I don't know other way, but I don't see what's wrong with this one? > > Hi Bastien, Sorry for replying too late (setup a filter on my Gmail account). Nothing wrong actually, except it's a minor visual distraction. So far I've only used a short unique tag like <<201009a>> (for today's date + letter) so it's not a major distraction.
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 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.
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, 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: 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? > > I cannot reproduce it on my side. What is the org-mode version you are > using? > > Best, > Ihor > > Samuel Wales writes: > >> === >> * x >> hi >> | >> there >> * y >> === >> >> if i copy x and yank it where | is, it yanks immediately above y. i >> prefer that it yanks at |. is this possible? >> >> is this new behavior? > -- The Kafka Pandemic Please learn what misopathy is. https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
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, Org release_9.4-38-g16f505
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' (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
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 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 signature.asc Description: PGP signature
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 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?
