From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: More clocktable breakage
Date: Sat, 06 May 2017 10:10:02 +0200 [thread overview]
Message-ID: <87pofmflt1.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87r307tb9k.fsf@Rainer.invalid> (Achim Gratz's message of "Tue, 02 May 2017 19:32:39 +0200")
Hello,
Achim Gratz <Stromeko@nexgo.de> writes:
> No, I meant context of application, rather than context in the
> syntactical sense. Org-element-* deals with syntax, nothing else.
> Whether you need strict syntactical interpretation or something else
> gets decided someplace else.
OK. Then we agree here.
> Whatever it sounds like, what you want in the clocktables example and
> the properties example (and elsewhere) is something that looks, walks
> and talks like a timestamp if you'd put it into the proper context. In
> each of these places the text that looks like timestamp but isn't
> (org-element says so) will be fed into some machinery that emerges with
> a result that is indistinguishable from what you'd get if that text
> would have been a proper timestamp and then uses that result to do
> whatever it wants to do with it (i.e. most certainly not build up an
> agenda, although it could do that as well). It uses a bit of Org syntax
> in the improper context to achieve this (and this requires precisely to
> ignore that context or at least check with something more loose than
> org-element).
I also agree, but it seems to contradict what you write below.
> In a comment that timestamp-looking text doesn't have any function, so
> it's in a different category, I must insist. As I said, I can see
> somebody wanting to have this text be editable like any other timestamp
> also, but it's really the other uses where it's used meta-syntactically
> that I'd like to focus on.
Here, I don't follow you anymore. A timestamp in a comment is "something
that looks, walks and talks like a timestamp if you'd put it into the
proper context", too. So there's no difference with properties or the
clock table.
> One of the differences to text in comments (or generally quoted
> material) is that there is an expectation that this sort of timestamp
> is correct, since they are intended to be input to further processing.
True, but if that timestamps isn't correct, it doesn't "look, walk and
talk" like a timestamp anymore, so this doesn't apply to the above.
Anyway, I think we're digressing. We're talking about design, yet, to
tell the truth, I don't even know anymore what the original, concrete,
problem is really about.
As I asked 5 weeks ago (!), could you provide an ECM demonstrating the
issue so that I can fix it, in the light of our discussion?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-05-06 8:10 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pofmflt1.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.