Improved fast selection of org-todo-keywords?

I like having a bunch of org-todo-keywords. > (setq org-todo-keywords '((sequence "TODO(t)" "TOREFILE(f)" "=====>(=)" "REMBER(m)" "NEXT(n!)" "PROJ(p)" "TOBEE(b)" "HABIT(h)" "RECUR(r)" "APPT(a)" "WAIT(w@!)" "WIP(k!)" "SOMEDAY(s!)" "ONEDAY(o!)" "HOLD(h@!)" "Z(z)" "|" "IDEA(i!)" "DONE(d!)" "DATA(a!)" "LOG(l!)" "CANCELED(c@!)" "JUMP(j!)"))) Even with fewer, it seems like using a single letter can force one to compromise due to similar letters. Is there a way to use two letters to select? Or maybe even better, an interactive auto-completion?

It's bold to suggest something like this without knowing your processes and workflows but did you think of moving some of those keywords from the list of keywords to tags? Potential candidates I would probably move would be: PROJ, HABIT, HOLD, IDEA, DATA?, LOG? and I would be interested in "APPT" because I'd get rid of it completely but you do seem to have a reason for that ...

I have a short list of keywords (four-character limit) to share: (setq org-todo-keywords '((sequence "TODO(t)" "NEXT(n!)" ; next action "DONE(d)" ; done) (sequence "WAIT(w@)" ; waiting to be actionable again "HOLD(h@/!)" ; actinable, but will do later "IDEA(i)" ; maybe someday "KILL(k@/!)" ; Task was cancelled, aborted or is no longer applicable)))

Thanks for sharing that! What I mean is, for example, what if I wanted to add the keyword "DEFER" (or any extra keyword that causes a conflict)? Now we have a conflict over the letter "D". I'd like to be able to type "DO" for DONE and "DE" for DEFER. Would be nice to have that as interactive completion as well. Many other areas of org allows for this functionality. Why wouldn't this allow for it? There must be some difference between the way this is implemented vs. the way other areas of org are implemented that can use completion. I'm not sure what the difference is.

Oh yes, not bold at all, and I totally agree. As a beginner, I'm only using one tag. I've barely scratched the surface of org. I have a certain very-base-level working system and workflow, and even with this, it's working for me better than anything in my life! (People in my family are saying, wow, you sure are productive lately!) There is sooo much to learn and improve upon, and I'm using org to help me plan on improving org. I've not yet set up or used archiving, and after I do that, I'm going to (learn about and then) set up something better than the default capture system. Better use of tags is down the line a bit. There's a method to my madness! I'm really just playing around with a set of TODO states, thinking about what I might use them for, how I might track different kinds of things with them. That said, I know I'm probably overloading my TODO keywords set, and some of this will be refactored in the future.

I'm using lower and capital letters for similar situations. E.g., d for DONE and D for deferred (not my use-case but you get the idea).

I didn't know that part of the system was case-sensitive. That helps a lot, thanks!