From: Arthur Miller <firstname.lastname@example.org>
To: Nick Dokos <email@example.com>
Subject: Re: Programmatically set TODO labels per file?
Date: Fri, 30 Apr 2021 12:13:12 +0200 [thread overview]
Message-ID: <AM9PR09MB497713FFAE5BBD98D85D4725965E9@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Nick Dokos's message of "Thu, 29 Apr 2021 21:08:41 -0400")
Nick Dokos <email@example.com> writes:
> Arthur Miller <firstname.lastname@example.org> writes:
>> I have a simple question, but I wasn't able to find answer on the web,
>> so finally I'll try my luck here.
>> I know I can setq org-todo-keywords with a list '((sequence "TODO"
>> DONE")), as an example. But what variable is used for per-file keywords?
>> Once that are set with #+TODO: ... line?
>> I guess when org mode parses a file when starting up the mode, it has to
>> parse that line into some var, where do I find it?
> It is parsed into a buffer-local variable by the name of
> `org-todo-keywords-1'. Do `C-h v org-todo-keywords' and `C-h v
> org-todo-keywords-1' for all the details.
> BTW, when the interwebs fail you (or even before that), use the source :-)
Yes indeed! I used the source Luke! :)
I found that one, unfortunately it is not enough to set that one to my
keywords. There are also two lists in play org-todo-kwd-alist and
org-todo-key-alist which are set in one mastodont method, but I think I
can refactor that out. I have to figure out how to build alist comming
from out org-collect-keywords which is input to that part of
code. Didn't had time last night, will see if I have time today.
next prev parent reply other threads:[~2021-04-30 10:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 20:49 Programmatically set TODO labels per file? Arthur Miller
2021-04-29 21:09 ` tomas
2021-04-29 21:58 ` Arthur Miller
2021-04-29 21:20 ` Russell Adams
2021-04-29 22:01 ` Arthur Miller
2021-04-29 22:37 ` Samuel Wales
2021-04-29 22:48 ` Arthur Miller
2021-04-30 1:08 ` Nick Dokos
2021-04-30 10:13 ` Arthur Miller [this message]
2021-04-30 14:35 ` Arthur Miller
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).