From: "Martin Carlé" <mc@aiguphonie.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] COMMENT-ed sections are tangled, if preceded by an org-todo keyword
Date: Mon, 12 Oct 2015 02:10:17 +0300 [thread overview]
Message-ID: <m1r3l1ngrq.fsf@aiguphonie.com> (raw)
In-Reply-To: <87egh1krtu.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 2512 bytes --]
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é <mc@aiguphonie.com> 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
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 805 bytes --]
prev parent reply other threads:[~2015-10-11 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 11:30 [BUG] COMMENT-ed sections are tangled, if preceded by an org-todo keyword Martin Carlé
2015-10-11 21:39 ` Nicolas Goaziou
2015-10-11 23:10 ` Martin Carlé [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1r3l1ngrq.fsf@aiguphonie.com \
--to=mc@aiguphonie.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).