From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: New exporter and dates in tables Date: Tue, 9 Apr 2013 15:06:53 +0200 Message-ID: <173ADFE7-A1FB-4ECB-A78A-C99662A8030F@gmail.com> References: <87fvz1opiz.fsf@norang.ca> <8761zxwlvn.fsf@gmail.com> <87bo9pntym.fsf@norang.ca> <0604BF00-1FE8-4EAA-A346-C125A5127CAD@gmail.com> <877gkcvm3n.fsf@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:32874) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UPYGK-00039D-V5 for emacs-orgmode@gnu.org; Tue, 09 Apr 2013 09:07:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UPYGG-0001SV-2g for emacs-orgmode@gnu.org; Tue, 09 Apr 2013 09:07:00 -0400 Received: from ezel.ic.uva.nl ([146.50.108.158]:48653) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UPYGF-0001RD-Qk for emacs-orgmode@gnu.org; Tue, 09 Apr 2013 09:06:56 -0400 In-Reply-To: <877gkcvm3n.fsf@gmail.com> 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: Bernt Hansen , emacs-orgmode@gnu.org On 8 apr. 2013, at 21:49, Nicolas Goaziou wrote: > Hello, >=20 > Carsten Dominik writes: >=20 >> On 8 apr. 2013, at 13:27, Bernt Hansen wrote: >>=20 >>> Nicolas Goaziou writes: >>>=20 >>>> Bernt Hansen writes: >>>>=20 >>>>> I have subtrees with inactive timestamps in the text indicating = when >>>>> something occurred. I normally don't want to export these. But I = think >>>>> any table data that includes inactive timestamps should be an = exception >>>>> to this ... otherwise you get output tables with blank cells where = the >>>>> meaningful timestamp data would be. >>>>=20 >>>> I understand. >>>>=20 >>>> So what exactly should be this exception? Should export ignore = <:nil >>>> option in a whole table, or only when a table cell contains a = single >>>> timestamp? IOW, how would it behaves in the following table: >>>>=20 >>>> | [2013-04-04 Thu] | Lunch at [2013-04-04 Thu] ] | >>>>=20 >>>> when `org-export-with-timestamps' is either nil or `active'? >>>=20 >>> I think keeping it simple is best. If there is an inactive = timestamp in >>> a table then it should be exported (I consider everything in a table = as >>> data). >>=20 >>=20 >> I think this is the right way to look at this. >=20 > I still find it surprising that <:nil will remove the timestamp in: >=20 > Lunch at [2013-04-04 Thu] >=20 > but not in >=20 > | Lunch at [2013-04-04 Thu] | >=20 > I suppose I'll eventually get it. Yes, I agree that it is hard to nail the exact reasons. The reasoning for me goes like this: Some people throw in time stamps often while they work, just as a little label, indicating that they were working on this at a specific date, or that the entry was created on a specific date. Many people I know have a hook that throws in such a time stamp in each new entry created. This creates a lot of clutter when you print it, which is why you can turn off export of timestamps. That option was not meant for a contextual line like your first example. If you use the time stamps in this way, you probably will not turn off timestamp export at all, you will just leave it on. If you mix both ways of using time stamps - well, too bad. Tabular data is different because you certainly wanted that data in the table, so removing it will be confusing. > Anyway, there's still another thing to ponder. Since everything in > a table is data, what happens with "tex:nil" (LaTeX snippets)? Should > this option also be ignored within a table? If not, how can we explain > the difference with "<:nil"? Tex macros are different. This is an internal way of inserting special characters, and that syntax may get into your way in some specific projects. Just like the fact that _ creates a subscript. If you have to write text with lots of _ but you never mean a subscript, this can be really annoying. So you can turn off subscripts as you can turn off interpretation of tex macros, as a convenience if the syntax gets in your way. Then it should be turned off anywhere, table or not. Regards - Carsten >=20 >=20 > Regards, >=20 > --=20 > Nicolas Goaziou