Re: [O] fast todo kw / - x
Hi Bastien, On 8/2/12, Bastien b...@gnu.org 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
Re: [O] fast todo kw / - x
Samuel Wales samolog...@gmail.com 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
Re: [O] fast todo kw / - x
On 7/14/12, Bastien b...@gnu.org 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 . ? - = + ( ) ' ; . Non-alpha are useful mnemonically for me. For example, ? is for QUESTION. I specify my keywords using a struct: (make-alpha-kw :key . :kw NEXTREPEAT :group :contingent :face '(:inherit org-todo :weight normal)) If I want modifiers, I add :mod. This gets mapped into the org-todo-keywords string. The advantage for me is that it keeps the keys and the modifier semantics separate. Also, it allows me to keep all keyword-related information, currently including faces and todo groups, together. The drawback for me is that org-todo-keywords combines the separate items into strings (so modifier symbols can't be used). :/ Allowing more symbols would be useful for me. If anybody wants the struct definition and mapper, I will extract and post them. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] fast todo kw / - x
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 semantics. :) My docstring does not mention close paren as having meaning in the same way / does. Not sure if docs need updating or not. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] fast todo kw / - x
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(?) EXPECT(E!) SUGU(g) CHUU(h!) ONGOING(o) WHENEVER(r) WHEN(W) STARTED(R) NEXT(n) NEXTKA(/) | MOSTKA(L) MOST(M) DONEKA(k) DONE(d) DUPLICATEKA(u) DUPLICATE(D) MOOTKA(K) MOOT(m) WAKARANAI(a) ASSERT(X Samuel, 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 would think that the quick keywords should be limited to word characters as defined by [[info:elisp#Char%20Classes][info:elisp#Char Classes]]. I bet if you provide suggested rewording for variable and info that someone on this will push it into the doc. Neil Smithline http://www.neilsmithline.com Proud GNU Emacs user since 1986, v. 18.24.
