From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Harkins Subject: SCHEDULED in a comment line is not ignored by sparse-tree Date: Wed, 03 Dec 2014 14:37:46 +0800 Message-ID: <87oarljl1h.wl-jamshark70@qq.com> Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36681) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xw3a2-0005Ey-L3 for emacs-orgmode@gnu.org; Wed, 03 Dec 2014 01:38:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xw3Zx-0006Wi-3D for emacs-orgmode@gnu.org; Wed, 03 Dec 2014 01:38:30 -0500 Received: from smtpbg64.qq.com ([103.7.28.238]:51591) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xw3Zt-0006Nv-HL for emacs-orgmode@gnu.org; Wed, 03 Dec 2014 01:38:25 -0500 Received: from hjh-e431.qq.com (unknown [219.136.2.59]) by esmtp4.qq.com (ESMTP) with SMTP id 0 for ; Wed, 03 Dec 2014 14:37:46 +0800 (CST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: orgmode 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