OK, thank you.
- Carsten
On 9.8.2013, at 13:02, Bernt Hansen be...@norang.ca wrote:
Hi Carsten!
All of my headings are followed by an inactive timestamp. I've started
leaving a blank line before the content for the heading so the inactive
timestamp is not exported when timestamps are
Hi guys,
did you arrive at a conclusion of this thread, or is this still open?
Thanks
- Carsten
On 16.4.2013, at 09:48, Bastien b...@gnu.org wrote:
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@gnu.org writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
We
Hi Carsten!
All of my headings are followed by an inactive timestamp. I've started
leaving a blank line before the content for the heading so the inactive
timestamp is not exported when timestamps are disabled with the :nil
option. This works fine for me.
Regards,
Bernt
Carsten Dominik
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@gnu.org writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
We can widen the definition of `standalone': a standalone timestamp is
a timestamp belonging to a paragraph that contains only timestamps
objects.
Great. If
Nicolas Goaziou n.goaz...@gmail.com writes:
The following patch should do that. It comes with tests, but it should
be tested extensively, if only to know if this feature is as useful as
it seems.
Thanks a lot. I will not be online for the next 5 hours, but I'll
think about this.
--
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@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
Sebastien Vauban
wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes:
Wouldn't it be a good moment to introduce
APPT: 2013-04-13 Sat
or maybe better named
EVENT: 2013-04-13 Sat
for things that only apply for today?
In master, there is the new agenda entry type :scheduled*
Hello,
Bastien b...@gnu.org writes:
Let's not implement my proposal and stick to your implementation of
the exceptions you first proposed.
Before we throw the baby out with the bath water, I want to make sure we
are understanding each other.
I expect users will want a way to get rid of
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
According to your suggestion, with `org-export-with-timestamps' set to
`not-standalone', in the following example:
* Task
timestamp
At timestamp, I must do that.
the first timestamp would be ignored, not the second one. Isn't it
Bastien b...@gnu.org writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
According to your suggestion, with `org-export-with-timestamps' set to
`not-standalone', in the following example:
* Task
timestamp
At timestamp, I must do that.
the first timestamp would be ignored, not the
Nicolas Goaziou n.goaz...@gmail.com writes:
Then why do you suggest to drop the idea (for now)?
Because IIUC, the time-stamps would not be ignored here
* Task
2013-04-14 dim.
2013-04-16 dim.
because
2013-04-14 dim.
2013-04-16 dim.
is a paragraph. (The agenda takes both time-stamps
Bastien b...@gnu.org writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Then why do you suggest to drop the idea (for now)?
Because IIUC, the time-stamps would not be ignored here
* Task
2013-04-14 dim.
2013-04-16 dim.
because
2013-04-14 dim.
2013-04-16 dim.
is a
Nicolas Goaziou n.goaz...@gmail.com writes:
We can widen the definition of `standalone': a standalone timestamp is
a timestamp belonging to a paragraph that contains only timestamps
objects.
Great. If that's possible, then I think that's the best solution.
--
Bastien
Nicolas
You may want to extract the below function as a useful API.
You can then plug that in into `org-odt--standalone-link-p' and it's
counterpart in ox-html.el.
I am not closely tracking changes in ox-html.el, so things might have
moved since.
Jambunathan K.
Nicolas Goaziou
Hello,
Bastien b...@gnu.org writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
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
Nicolas Goaziou n.goaz...@gmail.com writes:
Is that OK with you?
I still resist this idea.
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
When
Bastien b...@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
Hello,
Nicolas Goaziou wrote:
Bastien b...@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
Hello,
Bastien b...@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
Hello,
Nicolas Goaziou n.goaz...@gmail.com writes:
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
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
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
This looks good to me - with my limited understanding of the exporter lingo.
Thanks!
- Carsten
On 10 apr. 2013, at 14:43, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
Some people throw in time stamps often while they work, just
as
Hi all,
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
On 8 apr. 2013, at 21:49, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
On 8 apr. 2013, at 13:27, Bernt Hansen be...@norang.ca wrote:
Nicolas Goaziou n.goaz...@gmail.com writes:
Bernt Hansen be...@norang.ca writes:
I have
Hello,
Bernt Hansen be...@norang.ca writes:
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
Nicolas Goaziou n.goaz...@gmail.com writes:
Bernt Hansen be...@norang.ca writes:
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
On 8 apr. 2013, at 13:27, Bernt Hansen be...@norang.ca wrote:
Nicolas Goaziou n.goaz...@gmail.com writes:
Bernt Hansen be...@norang.ca writes:
I have subtrees with inactive timestamps in the text indicating when
something occurred. I normally don't want to export these. But I think
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
On 8 apr. 2013, at 13:27, Bernt Hansen be...@norang.ca wrote:
Nicolas Goaziou n.goaz...@gmail.com writes:
Bernt Hansen be...@norang.ca writes:
I have subtrees with inactive timestamps in the text indicating when
something
Hi Nicolas,
I just noticed that the new exporter does not export inactive timestamps
in table columns. This is now controlled by the option :t
I think this is a change from the old exporter (but I'm not sure it's
really wrong).
I have subtrees with inactive timestamps in the text indicating
On Apr 7, 2013, at 8:05 PM, Bernt Hansen be...@norang.ca wrote:
Hi Nicolas,
I just noticed that the new exporter does not export inactive timestamps
in table columns. This is now controlled by the option :t
I think this is a change from the old exporter (but I'm not sure it's
really
30 matches
Mail list logo
