Replies: 2 comments
-
I am that user 😊 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Workaround done meedstrom/org-mem@3a1cde4 Closing because it's inconsequential. The |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I confirm that...
I searched the FAQ, issue tracker, discussions board, documentation, and wiki, and found nothing about my issue.
I read the debugging guide and researched the issue to the best of my ability.
My issue can be observed on the latest available commit of Doom.
My issue can be observed on a stable release of Emacs (i.e. doesn't end in
.50,.60, or.9*)Describe your issue
I suppose that this hasn't broken anything important since its implementation ~8 years ago (doomemacs/doomemacs@03591ce77), given the lack of issues about it.
...but I want to raise the question. How would you express the
"[ ]"keyword (a member of Doom'sorg-todo-keywords) on a#+todo:line?If you type this in an Org file
then you can see in the resulting buffer-local value of
org-todo-regexpthat Org takes[and]as two separate keywords, not the string[ ]as one keyword.Reason I'm raising it now was that I wrote code that assumes that
org-todo-keywordscan't express anything more than what can be expressed on a#+todo:line (meedstrom/org-mem#18), so this led to mild breakage for at least one Doom user. I'll do a workaround, naturally, but maybe Doom wants to reconsider having this keyword at all?Or maybe upstream Org should even throw an error on seeing spaces in a keyword? Don't worry, I won't tilt at that windmill. Perhaps on the contrary, it should allow
[ ],< >,{ }etc as a special case...Also if it is already possible to express on a
#+todo:line, please let me know!Beta Was this translation helpful? Give feedback.
All reactions