Hi Bastien,
On 8/2/12, Bastien wrote:
> Actually I was wrong. All characters are supported for fast
> todo selection, except @ / and !. I've fixed the manual and
> the docstring.
Excellent, thank you!
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Hi Samuel,
Samuel Wales writes:
> On 7/14/12, Bastien wrote:
>> I updated a docstring and a part of the manual to make it
>> clearer only letters are supported.
>
> Thanks, Bastien. :) I appreciate the clarity in the manual.
Actually I was wrong. All characters are supported for fast
todo se
On 7/14/12, Bastien wrote:
> I updated a docstring and a part of the manual to make it
> clearer only letters are supported.
Thanks, Bastien. :) I appreciate the clarity in the manual.
Just so you know my use case:
I have 49 todo keywords and will have a few more soon, so I
will keep using . ?
Samuel Wales writes:
> NEXTKA below is selected by "x" instead of "/", which is surprising.
>
> Perhaps it's worth documenting the allowable keys?
I updated a docstring and a part of the manual to make it clearer
only letters are supported.
Thanks,
--
Bastien
Hi Neil,
"I definitely think that this is an omission in the doc. The doc for
`org-todo-keywords' ascribes meaning to at (@), slash (/), bang (!),
and at least close paren ())."
I find symbols useful, but I see now that / is used in that part. I
like plists as you can separate keys from semantic
On Sat May 19 21:35:28 2012, Samuel Wales wrote:
NEXTKA below is selected by "x" instead of "/", which is surprising.
Perhaps it's worth documenting the allowable keys?
(setf org-todo-keywords
'((type "REF(e)" "NAKA(i)" "META(=)" "GOAL(G)" "QUESTION(Q)"
"NOTE(O)" "TELL(+)" "ASK
