From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: can babel results show time of evaluation? Date: Wed, 30 Jan 2013 13:58:50 -0700 Message-ID: <87wquuz8tx.fsf@gmail.com> References: <87haly2aag.fsf@bzg.ath.cx> <87libawqb4.fsf@gmail.com> <87libao4r1.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:37444) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U0ekj-00080O-3f for emacs-orgmode@gnu.org; Wed, 30 Jan 2013 15:59:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U0ekg-0002B8-Ei for emacs-orgmode@gnu.org; Wed, 30 Jan 2013 15:59:28 -0500 Received: from mail-pb0-f50.google.com ([209.85.160.50]:39306) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U0ekg-0002B1-6x for emacs-orgmode@gnu.org; Wed, 30 Jan 2013 15:59:26 -0500 Received: by mail-pb0-f50.google.com with SMTP id ro8so1184333pbb.37 for ; Wed, 30 Jan 2013 12:59:25 -0800 (PST) In-Reply-To: <87libao4r1.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 30 Jan 2013 20:22:26 +0100") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: Bastien , emacs-orgmode@gnu.org, Thomas Alexander Gerds Nicolas Goaziou writes: > Hello, > > Eric Schulte writes: > >> I've just pushed this functionality up to the main branch. To make use >> of it add the following to your Emacs config. >> >> (setq org-babel-hash-show-time t) >> >> It works for me in some simple tests, and I can confirm that with this >> variable set to nil, I get no new failures in the Org-mode test suite, >> so it shouldn't introduce any problems. > > Well, it breaks the parser, somehow. Indeed, it expects from an > affiliated keyword such as #+results: (or #+caption for that matter) to > have only one secondary value. Sexp representation of these keywords is > already very complicated, it will not help to add values ad nauseum. > > Also, if you use Org time-stamp syntax, at some point, someone will ask > the parser to be able to parse it. And it won't. > > Eventually, it doesn't help to have hash syntax match Org links. This is > confusing. > > Therefore, if this feature really has to be introduced, I suggest, at > the very least, to avoid using Org regular syntax for the reference to > time. It would also help to blur distinction between the time and the > hash string. Perhaps something like the following: > > #+results[2013-01-30T20:15:37 hash-string]: name > > Thank you. > Are there instances aside from "#+results" where one would want to pack ancillary information into a keyword? Perhaps both the hash and the time should be moved *outside* the keyword, e.g. something like the following, #+Results: name time hash What do you think? > > > Regards, -- Eric Schulte http://cs.unm.edu/~eschulte