From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastien Vauban Subject: Re: SCHEDULED in a comment line is not ignored by sparse-tree Date: Wed, 03 Dec 2014 15:54:09 +0100 Message-ID: <86zjb4pywe.fsf@example.com> References: <87oarljl1h.wl-jamshark70@qq.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org James Harkins wrote: > This appears to be buggy behavior, but I'm asking here first in case > it might already have been fixed. [...] > > #+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 > > 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. I had reported that very same issue in May 2014: http://lists.gnu.org/archive/html/emacs-orgmode/2014-05/msg00756.html Still there... Best regards, Seb -- Sebastien Vauban