emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Neil Smithline <emacs-orgmode@neilsmithline.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: [BUG] Org Mode Bug With #+TODO In-Buffer Setting
Date: Sat, 18 Aug 2012 15:40:48 -0400	[thread overview]
Message-ID: <502FEFC0.4010507@neilsmithline.com> (raw)

Org Mode doesn't completely ignore lines with a `TODO' in-buffer setting 
that have a space between the hash and plus sign. The file and the 
instructions for reproducing this are in the gist below. I recommend 
grabbing the raw gist to avoid Github formatting (it seems to like to 
format plain text files).

IMO, a strange bug. For some uses the lines with a hash-space-plus are 
correctly treated as plain lines while in other cases they are 
incorrectly treated as legal in-buffer setting lines.


PS: I didn't think of checking when I posted the gist but the same 
problem seems to occur for other tags. I just tested it on `FILETAGS' 

[gist]     - https://gist.github.com/3389206
[raw gist] - 
Neil Smithline

             reply	other threads:[~2012-08-18 19:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18 19:40 Neil Smithline [this message]
2012-08-19  7:01 ` Bastien

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:

  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=502FEFC0.4010507@neilsmithline.com \
    --to=emacs-orgmode@neilsmithline.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: [BUG] Org Mode Bug With #+TODO In-Buffer Setting' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).