Hello,
John Hendy writes:
> Will do. Given that I apparently have it off (sorry, haven't had time
> to check yet), is the purpose of <:t/nil to purely allow plain
> timestamps by default and let the user opt-in to scheduled/deadlines?
<:t (or `org-export-with-timestamps') is about isolated time
On Fri, Jun 21, 2013 at 4:58 PM, Nicolas Goaziou wrote:
> Hello,
>
> John Hendy writes:
>
>> One more update... I had the idea to try a regular timestamp, and
>> those export, even though SCHEDULED and DEADLINE do not. Lastly, I
>> used a minimal config and emacs -Q and get the same behavior:
>>
Hello,
John Hendy writes:
> One more update... I had the idea to try a regular timestamp, and
> those export, even though SCHEDULED and DEADLINE do not. Lastly, I
> used a minimal config and emacs -Q and get the same behavior:
>
> #+begin_src min-config
> (add-to-list 'load-path "~/.elisp/org.gi
On Fri, Jun 21, 2013 at 3:47 PM, John Hendy wrote:
> On Fri, Jun 21, 2013 at 3:41 PM, John Hendy wrote:
>> I have the following options line in my file header:
>>
>> #+options: <:t num:t author:t tags:t toc:nil tasks:t todo:t
>>
>> Sample file:
>>
>> #+begin_src org
>> #+options: <:t num:t author
On Fri, Jun 21, 2013 at 3:41 PM, John Hendy wrote:
> I have the following options line in my file header:
>
> #+options: <:t num:t author:t tags:t toc:nil tasks:t todo:t
>
> Sample file:
>
> #+begin_src org
> #+options: <:t num:t author:t tags:t toc:nil tasks:t todo:t
>
> * Task list
>
> ** todo t
I have the following options line in my file header:
#+options: <:t num:t author:t tags:t toc:nil tasks:t todo:t
Sample file:
#+begin_src org
#+options: <:t num:t author:t tags:t toc:nil tasks:t todo:t
* Task list
** todo task 1
DEADLINE: <2013-06-21 Fri>
** todo task 2
SCHEDULED: <2013
