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: Sat, 13 Apr 2013 19:33:17 +0200 [thread overview]
Message-ID: <87ehee9vz6.fsf@gmail.com> (raw)
In-Reply-To: <874nfa34vj.fsf@bzg.ath.cx> (Bastien's message of "Sat, 13 Apr 2013 16:02:56 +0200")
Bastien <bzg@gnu.org> writes:
> I would find it both cleaner and more useful for users to extend
> `org-export-with-timestamps' with three choices:
>
> 'inactive-not-standalone
> 'active-not-standalone
> 'not-standalone
This is a different idea. The change would happen at the exporter level,
not at parser's.
> When set to 'not-standalone, it means export time-stamps except
> "standone time-stamps", i.e. those who are alone on a line.
Well, parsing is not line based, and "a timestamp alone on a line"
doesn't mean much. Though, "a timestamp alone in a paragraph" is much
easier to translate. IOW:
<2013-04-13 Sat>
is not a standalone timestamp (use M-q).
but,
<2013-04-13 Sat>
is a standalone timestamp.
> That's the set-up most users will want after t, it fits the habits
> that Bernt has been describing, and it's useful for users who wants to
> get rid of the planning-like active time-stamp right below the
> headline.
>
> Also, it's easier to explain users how to set this up (through
> the docstring) than to explain why time-stamps are not removed in
> tables with (setq org-export-with-timestamps nil).
If we agree to the "alone in a paragraph" part, I can implement it.
But we still need exceptions for clocks and timestamps (i.e., ignore
`org-export-with-timestamps' value when `org-export-with-planning' or
`org-export-with-clocks' is non-nil).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-04-13 17:33 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
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 [this message]
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=87ehee9vz6.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).