[O] [BUG] COMMENT-ed sections are tangled, if preceded by an org-todo keyword

[Martin Carlé]

Hello,

sections or subtrees commented with org-comment-string in the headline
should not be tangled. This works fine.

However, if a tag defined in org-todo-keywords (other than TODO or DONE)
precedes the comment (as the official syntax has it), commenting is no
longer respected such that source-blocks in the section/subtree are tangled.

I think this cannot be intentional and is probably a bug.

Best regards,
mc


For example:

* TODO COMMENT this headline should not be tangled
#+begin_src emacs-lisp 
  (message "I am COMMENT-ed and thus I am not tangled - OK")
#+end_src

* WATCH COMMENT this headline should not be tangled
#+begin_src emacs-lisp 
  (message "I am COMMENT-ed but a I still tangled - FALSE")
#+end_src


-- 
Fetch my gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 7E3CA33F


smime.p7s
Description: S/MIME cryptographic signature

Re: [O] [BUG] COMMENT-ed sections are tangled, if preceded by an org-todo keyword

[Martin Carlé]

Thank you for looking into that issue!

I trace the git repo of org-mode (current commit is 50a18201).

My todo-keywords are not defined file-local but during emacs startup like this:


,---
| (setq org-todo-keywords
| '((sequence "TODO(t)" "|" "DONE(d)")
|   (sequence "DOIT(i!)" "FEEDBACK(e@/!)" "LINGER(l@/!)" "VERIFY(v!)" 
"|" "OVER(o!)" "DELEGATED(g@/!)")
|   (sequence "BUG(b!)" "ASK(a)" "REPORT(r)" "KNOWNCAUSE(k!)" 
"WATCH(w!)" "|" "STRANGE(s!)"  "FIXED(f@/!)") 
|   (sequence "|" "CANCELED(c@)")  
|   (sequence "THINKof(T)" "CHECK(K)" "OPTIMIZE(O)" "CONTINUE(C)" 
"REPEAT(R)" "MAYBE(M)" "|" "PERFECTED(P)")
|   (sequence "TODOs" "|" "DONEs") 
|   ))  
`---

Maybe that's the reason why it couldn't be reproduced.
Or do I missed something while setting the var "org-todo-keywords"?

Best regards,
mc


On 2015-10-12T00:39:41+0300, spake thus:
> Hello,

> Martin Carlé  writes:

> > sections or subtrees commented with org-comment-string in the headline
> > should not be tangled. This works fine.
> >
> > However, if a tag defined in org-todo-keywords (other than TODO or DONE)
> > precedes the comment (as the official syntax has it), commenting is no
> > longer respected such that source-blocks in the section/subtree are tangled.
> >
> > I think this cannot be intentional and is probably a bug.
> >
> > Best regards,
> > mc
> >
> >
> > For example:
> >
> > * TODO COMMENT this headline should not be tangled
> > #+begin_src emacs-lisp 
> >   (message "I am COMMENT-ed and thus I am not tangled - OK")
> > #+end_src
> >
> > * WATCH COMMENT this headline should not be tangled
> > #+begin_src emacs-lisp 
> >   (message "I am COMMENT-ed but a I still tangled - FALSE")
> > #+end_src

> I cannot reproduce the problem. Did you properly activate new TODO
> keyword, e.g., using C-c C-c on the #+TODO: WATCH line?

> Also, what is Org's version ?


> Regards,

> -- 
> Nicolas Goaziou


-- 
Fetch my gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 7E3CA33F


smime.p7s
Description: S/MIME cryptographic signature

Re: [O] [BUG] COMMENT-ed sections are tangled, if preceded by an org-todo keyword

[Nicolas Goaziou]

Hello,

Martin Carlé  writes:

> sections or subtrees commented with org-comment-string in the headline
> should not be tangled. This works fine.
>
> However, if a tag defined in org-todo-keywords (other than TODO or DONE)
> precedes the comment (as the official syntax has it), commenting is no
> longer respected such that source-blocks in the section/subtree are tangled.
>
> I think this cannot be intentional and is probably a bug.
>
> Best regards,
> mc
>
>
> For example:
>
> * TODO COMMENT this headline should not be tangled
> #+begin_src emacs-lisp 
>   (message "I am COMMENT-ed and thus I am not tangled - OK")
> #+end_src
>
> * WATCH COMMENT this headline should not be tangled
> #+begin_src emacs-lisp 
>   (message "I am COMMENT-ed but a I still tangled - FALSE")
> #+end_src

I cannot reproduce the problem. Did you properly activate new TODO
keyword, e.g., using C-c C-c on the #+TODO: WATCH line?

Also, what is Org's version ?


Regards,

-- 
Nicolas Goaziou