From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: More clocktable breakage
Date: Thu, 27 Apr 2017 20:56:12 +0200 [thread overview]
Message-ID: <8737ct1xyr.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87shkt4tuf.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 27 Apr 2017 19:56:56 +0200")
Achim Gratz <Stromeko@nexgo.de> writes:
> Achim Gratz writes:
>> 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
These are not timestamps. Even though they look like timestamps, you
wouldn't want them to appear in the agenda. So `org-at-timestamp-p' is
correct, IMO. Moreover, its docstring says
This function checks context and only return non-nil for valid
time stamps. If you need to match anything looking like a time
stamp, or if you are sure about the context, consider using
‘org-in-regexp’, e.g.,
(org-in-regexp org-ts-regexp)
so ISTM a correct fix would be to have the function you're calling (I
don't remember it) use this instead of `org-at-timestamp-p'.
WDYT?
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-04-27 18:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 19:24 More clocktable breakage Achim Gratz
2017-03-29 14:38 ` Nicolas Goaziou
2017-04-26 17:09 ` Achim Gratz
2017-04-27 17:56 ` Achim Gratz
2017-04-27 18:56 ` Nicolas Goaziou [this message]
2017-04-27 20:09 ` Achim Gratz
2017-04-27 22:49 ` Nicolas Goaziou
2017-04-28 18:56 ` Achim Gratz
2017-04-30 7:21 ` Nicolas Goaziou
2017-05-01 8:27 ` Achim Gratz
2017-05-02 16:47 ` Nicolas Goaziou
2017-05-02 17:32 ` Achim Gratz
2017-05-06 8:10 ` Nicolas Goaziou
2017-05-06 9:53 ` Achim Gratz
2017-05-07 10:15 ` Nicolas Goaziou
2017-05-07 10:36 ` Achim Gratz
2017-05-14 9:10 ` Nicolas Goaziou
2017-05-14 9:50 ` Achim Gratz
2017-05-15 16:28 ` Achim Gratz
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=8737ct1xyr.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=Stromeko@nexgo.de \
--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).