From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: More clocktable breakage Date: Sun, 07 May 2017 12:36:30 +0200 Message-ID: <87lgq9hs29.fsf@Rainer.invalid> References: <877f39nr05.fsf@Rainer.invalid> <87d1d0p2qx.fsf@nicolasgoaziou.fr> <87tw5bumck.fsf@Rainer.invalid> <87shkt4tuf.fsf@Rainer.invalid> <8737ct1xyr.fsf@nicolasgoaziou.fr> <87fugt4npu.fsf@Rainer.invalid> <87pofxzctf.fsf@nicolasgoaziou.fr> <87wpa4fjio.fsf@Rainer.invalid> <878tmixsvo.fsf@nicolasgoaziou.fr> <87tw556kxo.fsf@Rainer.invalid> <87vapjgq93.fsf@nicolasgoaziou.fr> <87r307tb9k.fsf@Rainer.invalid> <87pofmflt1.fsf@nicolasgoaziou.fr> <87inle8g5s.fsf@Rainer.invalid> <87vapd6khx.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47818) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d7JYT-0003FP-4f for emacs-orgmode@gnu.org; Sun, 07 May 2017 06:36:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d7JYO-0007Ss-80 for emacs-orgmode@gnu.org; Sun, 07 May 2017 06:36:45 -0400 Received: from [195.159.176.226] (port=56485 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d7JYO-0007So-0v for emacs-orgmode@gnu.org; Sun, 07 May 2017 06:36:40 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1d7JYE-0006GJ-5F for emacs-orgmode@gnu.org; Sun, 07 May 2017 12:36:30 +0200 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" To: emacs-orgmode@gnu.org Nicolas Goaziou writes: > OK. I inserted it in a fresh Org buffer. Is there any command to call on > it now? Yes, put the cursor on the date or time of one of the timestamps and press S-Up or S-Down. It should increase or decrease the corresponding element of the timestamp, but instead you'll get an error message: org-clocktable-shift: Line needs a :block definition before this command works which appears because the timestamp wasn't recognized and the fallthrough of org-shift* then tries to apply another function that deals with the :block argument (which isn't present here and shouldn't be). >> Sometimes org-element-context recognizes the clocktable as a paragraph >> instead of dynamic-block > > FWIW, I get `dynamic-block'. OK, then that should get you the same error. >> (I've not yet figured out why and it isn't vary reproducible, but it >> must have something to do with the cache since it goes away when >> I reload the file) > > It is possible, indeed. You can also use M-x org-element-cache-reload to > check this. However, cache is disabled by default, so the problem > shouldn't appear in normal usage. I have not enabled any cache that I know of. All I can say is that sometimes the clocktable doesn't get recognized as dynamic-block but a paragraph instead. That re-enables the recognition of the timestamp incidentally (why exactly I don't really understand), which was why I couldn't reproduce the error at home for some time. > I start to think that there is no bug in clock tables (but certainly in > the cache mechanism, probably related to some `before-change-functions' > and `after-change-functions' misuse there). I'm not using any of those unless they already come with Emacs or Org. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada