Hi Brian,
Brian van den Broek brian.van.den.br...@gmail.com writes:
Hi Bastien and all,
I am afriad you saw this coming:
I somehow was, but I played ostrich here :)
Could that be an option? I actively would want to preserve the closed
note to keep an accurate history of my work with the
On 4/12/13, Bastien b...@gnu.org wrote:
I'm convinved now, and switching to state without any TODO keyword
will now remove the CLOSED planning information.
Thanks, Bastien. One of the great things about Org is its attention
to detail, and that includes little orthogonality pieces.
Samuel
--
On 12 Apr 2013 11:58, Bastien b...@gnu.org wrote:
Hi Samuel,
I'm convinved now, and switching to state without any TODO keyword
will now remove the CLOSED planning information.
Thanks,
--
Bastien
Hi Bastien and all,
I am afriad you saw this coming:
Could that be an option? I actively
Hi Samuel,
I'm convinved now, and switching to state without any TODO keyword
will now remove the CLOSED planning information.
Thanks,
--
Bastien
Hi Bastien,
On 4/10/13, Bastien b...@gnu.org wrote:
Changing a doneified entry to blank todo state leaves a
closed ts.
#+BEGIN_SRC org
,* DONE doneify
CLOSED: [2013-04-09 Tue 14:11]
,* now change to blank todo kw -- notice the closed ts
CLOSED: [2013-04-09 Tue 14:11]
#+END_SRC
Hi Samuel,
Samuel Wales samolog...@gmail.com writes:
Changing a doneified entry to blank todo state leaves a
closed ts.
#+BEGIN_SRC org
,* DONE doneify
CLOSED: [2013-04-09 Tue 14:11]
,* now change to blank todo kw -- notice the closed ts
CLOSED: [2013-04-09 Tue 14:11]
#+END_SRC
Changing a doneified entry to blank todo state leaves a
closed ts.
#+BEGIN_SRC org
,* DONE doneify
CLOSED: [2013-04-09 Tue 14:11]
,* now change to blank todo kw -- notice the closed ts
CLOSED: [2013-04-09 Tue 14:11]
#+END_SRC
Perhaps it would be more intuitive for newcomers, and safer