emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Bernt Hansen <bernt@norang.ca>,
	emacs-orgmode@gnu.org,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: New exporter and dates in tables
Date: Thu, 11 Apr 2013 13:28:00 +0200	[thread overview]
Message-ID: <87d2u1s3wf.fsf@gmail.com> (raw)
In-Reply-To: <87bo9mh6ex.fsf@bzg.ath.cx> (Bastien's message of "Wed, 10 Apr 2013 15:16:54 +0200")

Hello,

Bastien <bzg@gnu.org> writes:

> Note that Org 8.0-pre comes with a new export option
> `org-export-with-planning' which handles the export of
> SCHEDULED / DEADLINE / CLOSED time-stamps.
>
> This used to be the job of org-export-with-timestamps.
>
> I guess many people who used (setq org-export-with-timestamps nil)
> now want (setq org-export-with-planning nil) and which works well
> with (setq org-export-with-timestamps 'inactive).
>
> So I'm wondering: would the setup above spare us with this exception?
>
> I know people sometimes throw inactive time-stamps, but those small
> indications would better fit in a commented line.
>
> WDYT?

Thinking more about it, I think I need to make some more exceptions
anyway. For example timestamps in clock lines and in planning info
shouldn't react to `org-export-with-timestamps' (it would be silly to
have `org-export-with-planning' set to t and still see nothing because
`org-export-with-timestamps' is nil).

After all, this exception may not be that exceptional.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-04-11 11:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08  0:05 New exporter and dates in tables Bernt Hansen
2013-04-08  2:18 ` Mike McLean
2013-04-08  6:57 ` Nicolas Goaziou
2013-04-08 11:27   ` Bernt Hansen
2013-04-08 11:33     ` Carsten Dominik
2013-04-08 19:49       ` Nicolas Goaziou
2013-04-09 13:06         ` Carsten Dominik
2013-04-10 12:43           ` Nicolas Goaziou
2013-04-10 13:12             ` Carsten Dominik
2013-04-10 13:16             ` Bastien
2013-04-11 11:28               ` Nicolas Goaziou [this message]
2013-04-11 15:49                 ` Bastien
2013-04-13 10:54                   ` Nicolas Goaziou
2013-04-13 14:02                     ` Bastien
2013-04-13 17:33                       ` Nicolas Goaziou
2013-04-13 21:07                         ` Sebastien Vauban
2013-04-14  9:10                           ` Bastien
2013-04-14  8:58                         ` Bastien
2013-04-14 13:37                           ` Nicolas Goaziou
2013-04-14 13:45                             ` Bastien
2013-04-14 13:47                               ` Nicolas Goaziou
2013-04-14 14:01                                 ` Bastien
2013-04-14 14:06                                   ` Nicolas Goaziou
2013-04-14 14:24                                     ` Bastien
2013-04-14 20:36                                       ` Nicolas Goaziou
2013-04-15  3:58                                         ` Jambunathan K
2013-04-15  6:44                                         ` Bastien
2013-04-16  7:48                                         ` Bastien
2013-08-09  9:35                                           ` Carsten Dominik
2013-08-09 11:02                                             ` Bernt Hansen
2013-08-12  5:45                                               ` Carsten Dominik

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=87d2u1s3wf.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=bernt@norang.ca \
    --cc=bzg@gnu.org \
    --cc=carsten.dominik@gmail.com \
    --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).