emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins <jamshark70@qq.com>
To: orgmode <emacs-orgmode@gnu.org>
Subject: SCHEDULED in a comment line is not ignored by sparse-tree
Date: Wed, 03 Dec 2014 14:37:46 +0800	[thread overview]
Message-ID: <87oarljl1h.wl-jamshark70@qq.com> (raw)

This appears to be buggy behavior, but I'm asking here first in case it might already have been fixed.

A couple of months ago, I was trying to create a repeating timestamp for two different days of the week. First I tried a diary-sexp, but that wasn't compatible with habits, so I gave that up. But I didn't want to throw away the string completely, because it took some digging to figure it out. So I put "# " at the beginning of the SCHEDULED line and thought that would be the end of it. (In the source block, "#" has two spaces before it. These come from C-c ' editing. In my original file, the "#" for the comment is flush left.)

#+BEGIN_SRC org
  ,** TODO Update lesson grades 2                                         :Comp:
     SCHEDULED: <2014-12-06 Sat 23:59 .+1w>
     :PROPERTIES:
     :STYLE:    habit
     :LOGGING:  TODO MAYBE INPROG MTG | DONE(!) POSTPONED CANCELED
     :END:
  #   SCHEDULED: <%%(memq (calendar-day-of-week date) '(3 6))>
#+END_SRC

Just now, I tried to open a sparse-tree view with a scheduled date range -- C-c / c c D (set range) -- and got the message:

byte-code: Bad timestamp `%%(memq (calendar-day-of-week date) '(3 6))'
Error was: (Not a standard Org-mode time string: %%(memq (calendar-day-of-week date) '(3 6)))

This is the only occurrence of memq anywhere in this org file, so it *must* be coming from this line. So, whatever regexp is handling scheduled timestamp searches doesn't check whether the line is a comment or not.

There may be a valid reason for this behavior, but I tend to think a comment should always be a comment.

hjh

             reply	other threads:[~2014-12-03  6:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  6:37 James Harkins [this message]
2014-12-03 14:54 ` SCHEDULED in a comment line is not ignored by sparse-tree Sebastien Vauban
2014-12-23 11:24 ` Nicolas Goaziou

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=87oarljl1h.wl-jamshark70@qq.com \
    --to=jamshark70@qq.com \
    --cc=emacs-orgmode@gnu.org \
    /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).