emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Arthur Miller <arthur.miller@live.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Programmatically set TODO labels per file?
Date: Thu, 29 Apr 2021 15:37:50 -0700	[thread overview]
Message-ID: <CAJcAo8sib=y7n_vRVjYEZpx5CZxieYs8Tnud0WXPT6qo0Qes0w@mail.gmail.com> (raw)
In-Reply-To: <AM9PR09MB49778D454A5D708BCCF737C0965F9@AM9PR09MB4977.eurprd09.prod.outlook.com>

as you discovered, spaces can work for todo kw for at least some
purposes.  [i have one, because i prefer space to snake_case and
kebab-case might not search well.]  but you should check to see if it
is guaranteed to work.  i vaguely recall spc is not allowable.

if it were guaranteed to work, then there would likely be a mechanism
to include it in the #+ syntax.  :)


On 4/29/21, Arthur Miller <arthur.miller@live.com> wrote:
> Russell Adams <RLAdams@AdamsInfoServ.Com> writes:
>
>> On Thu, Apr 29, 2021 at 10:49:54PM +0200, Arthur Miller wrote:
>>>
>>> Hi all,
>>>
>>> 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?
>>>
>>> Thanks in advance!
>>>
>>> Best regards
>>> /a
>>>
>>
>> https://orgmode.org/manual/Per_002dfile-keywords.html
>
> Thanks Rusell; but I have seen the manual as I wrote. I am aware I can
> use
>
> #+TODO:
>
> syntax to set per file keywords. I wanted to do this from lisp, since I
> can't use labels with multiple words with that syntax since spaces are
> used as delimiters for keywords, but I can pass strings (with spaces)
> with lisp.
>
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html


  reply	other threads:[~2021-04-29 22:38 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 [this message]
2021-04-29 22:48       ` Arthur Miller
2021-04-30  1:08 ` Nick Dokos
2021-04-30 10:13   ` Arthur Miller
2021-04-30 14:35     ` Arthur Miller

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJcAo8sib=y7n_vRVjYEZpx5CZxieYs8Tnud0WXPT6qo0Qes0w@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=arthur.miller@live.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).