Re: More clocktable breakage

[Achim Gratz <Stromeko@nexgo.de>]

Nicolas Goaziou writes:
> At the moment, I cannot reproduce it. I tried M-up in the following
> document:
>
>      #+BEGIN: clocktable :tstart "<2006-08-10 Thu 10:00>" :tend "<2006-08-10 Thu 12:00>"
>      #+END: clocktable

The breakage happens in this clause in org-at-timestamp-p:

--8<---------------cut here---------------start------------->8---
	 (match
	  (let ((boundaries (org-in-regexp tsr)))
	    (save-match-data
	      (cond ((null boundaries) nil)
		    ((org-at-planning-p))
		    ((org-at-property-p))
		    ;; CLOCK lines only contain inactive time-stamps.
		    ((and inactive-ok (org-at-clock-log-p)))
		    (t
		     (eq 'timestamp
			 (save-excursion
			   (when (= pos (cdr boundaries)) (forward-char -1))
			   (org-element-type (org-element-context))))))))))
--8<---------------cut here---------------end--------------->8---

After matching the timestamp in the header argument correctly, the code
falls through to the default cond, where (org-element-type
(org-element-context)) returns 'dynamic-block, which isn't a 'timestamp.
The successful match gets discarded and the timestamp doesn't get
recognized.  An empty clause for (org-at-block-p) would fix it, but I'm
not sure that is the right thing to do.  I haven't looked at
org-element-context to see whether it might misinterpret something.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada