* logdone enhancement
@ 2013-02-27 6:21 Arun Persaud
2013-02-27 8:33 ` Bastien
0 siblings, 1 reply; 9+ messages in thread
From: Arun Persaud @ 2013-02-27 6:21 UTC (permalink / raw)
To: emacs-orgmode
Hello
if I have something like the following
#+STARTUP: logdone
* project
** TODO headline :repeat:
a longer description of what the todo item is about
SCHEDULED: <2013-06-18 Tue +1m>
- State "DONE" from "WAITING" [2013-02-26 Tue 21:56]
- State "DONE" from "WAITING" [2013-01-14 Mon 18:18]
- State "DONE" from "WAITING" [2012-09-30 Sun 19:36]
- State "DONE" from "WAITING" [2012-09-02 Sun 10:28]
- State "DONE" from "WAITING" [2012-06-28 Thu 11:08]
- State "DONE" from "WAITING" [2012-05-07 Mon 10:56]
....
and then cycle through the TODO states the new '- State "Done"...'
message shows up between the headline and the description. Is there a
way to always add the new line after the SCHEDULED or perhaps better
before the first log-message in the task? That way they could be kept
easily at any position in the task.
Thanks
Arun
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: logdone enhancement
2013-02-27 6:21 logdone enhancement Arun Persaud
@ 2013-02-27 8:33 ` Bastien
2013-02-27 9:15 ` Sebastien Vauban
2013-02-27 18:39 ` Arun Persaud
0 siblings, 2 replies; 9+ messages in thread
From: Bastien @ 2013-02-27 8:33 UTC (permalink / raw)
To: Arun Persaud; +Cc: emacs-orgmode
Hi Arun,
Arun Persaud <apersaud@lbl.gov> writes:
> * project
> ** TODO headline :repeat:
> a longer description of what the todo item is about
> SCHEDULED: <2013-06-18 Tue +1m>
The SCHEDULED line should be right after the headline, see the manual.
It can sometimes work when it is on another line, but this is
accidental, you should put the line right after the headline.
HTH,
--
Bastien
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: logdone enhancement
2013-02-27 8:33 ` Bastien
@ 2013-02-27 9:15 ` Sebastien Vauban
2013-02-27 9:25 ` Bastien
2013-02-27 18:39 ` Arun Persaud
1 sibling, 1 reply; 9+ messages in thread
From: Sebastien Vauban @ 2013-02-27 9:15 UTC (permalink / raw)
To: emacs-orgmode-mXXj517/zsQ
Hi Bastien,
Bastien wrote:
> Arun Persaud <apersaud-/3juihCSby0@public.gmane.org> writes:
>
>> * project
>> ** TODO headline :repeat:
>> a longer description of what the todo item is about
>> SCHEDULED: <2013-06-18 Tue +1m>
>
> The SCHEDULED line should be right after the headline, see the manual.
> It can sometimes work when it is on another line, but this is
> accidental, you should put the line right after the headline.
Now that this "syntax order" is enforced, will we get commit 6b04bef back in
Org 8? That'd be great...
Best regards,
Seb
PS- See discussion on
http://lists.gnu.org/archive/html/emacs-orgmode/2011-08/msg01248.html
and https://lists.gnu.org/archive/html/emacs-orgmode/2011-09/msg00219.html
--
Sebastien Vauban
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: logdone enhancement
2013-02-27 9:15 ` Sebastien Vauban
@ 2013-02-27 9:25 ` Bastien
2013-02-27 10:04 ` Sebastien Vauban
0 siblings, 1 reply; 9+ messages in thread
From: Bastien @ 2013-02-27 9:25 UTC (permalink / raw)
To: Sebastien Vauban; +Cc: public-emacs-orgmode-mXXj517/zsQ
Hi Sébastien,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> Now that this "syntax order" is enforced, will we get commit 6b04bef back in
> Org 8? That'd be great...
Why not. Can you heavily test commit 6b04bef and see if
anything goes wrong?
--
Bastien
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: logdone enhancement
2013-02-27 9:25 ` Bastien
@ 2013-02-27 10:04 ` Sebastien Vauban
2013-02-27 12:22 ` Bastien
0 siblings, 1 reply; 9+ messages in thread
From: Sebastien Vauban @ 2013-02-27 10:04 UTC (permalink / raw)
To: emacs-orgmode-mXXj517/zsQ
Bastien,
Bastien wrote:
> Hi Sébastien,
>
> "Sebastien Vauban"
> <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>> Now that this "syntax order" is enforced, will we get commit 6b04bef back in
>> Org 8? That'd be great...
>
> Why not. Can you heavily test commit 6b04bef and see if
> anything goes wrong?
I can try, though it already had been heavily tested back in that time.
But first, For me, the question comes down to: do we agree that John (in this
case) won't be allowed anymore to write such an entry?
--8<---------------cut here---------------start------------->8---
*** NOTE Assets:Receivable:CEG
#+begin_src sh :results value :exports results
ledger reg --inject=Expected '^income:ceg'
ledger reg --sort date -b 2007 receivable:CEG
#+end_src
:PROPERTIES:
:ID: 8BEF6C42-8B23-495B-9421-3810B58907A1
:VISIBILITY: folded
:CREATED: [2010-06-18 Fri 07:37]
:END:
--8<---------------cut here---------------end--------------->8---
Best regards,
Seb
--
Sebastien Vauban
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: logdone enhancement
2013-02-27 10:04 ` Sebastien Vauban
@ 2013-02-27 12:22 ` Bastien
0 siblings, 0 replies; 9+ messages in thread
From: Bastien @ 2013-02-27 12:22 UTC (permalink / raw)
To: Sebastien Vauban; +Cc: public-emacs-orgmode-mXXj517/zsQ
Hi Sébastien,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> But first, For me, the question comes down to: do we agree that John (in this
> case) won't be allowed anymore to write such an entry?
>
> *** NOTE Assets:Receivable:CEG
> #+begin_src sh :results value :exports results
> ledger reg --inject=Expected '^income:ceg'
> ledger reg --sort date -b 2007 receivable:CEG
> #+end_src
> :PROPERTIES:
> :ID: 8BEF6C42-8B23-495B-9421-3810B58907A1
> :VISIBILITY: folded
> :CREATED: [2010-06-18 Fri 07:37]
> :END:
No. The rule is about the SCHEDULED line, not about the :PROPERTIES:
drawer. So John is allowed to write such an entry.
`org-fixup-indentation' is just a way to _improve_ the indentation,
so it should do its best in order to align SCHEDULED cookies (and
friends) *and* drawers. If it can't align some drawers, it should
just ignore them. And be happy with what it did.
Thanks for testing,
--
Bastien
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: logdone enhancement
2013-02-27 8:33 ` Bastien
2013-02-27 9:15 ` Sebastien Vauban
@ 2013-02-27 18:39 ` Arun Persaud
2013-02-27 19:08 ` Nick Dokos
1 sibling, 1 reply; 9+ messages in thread
From: Arun Persaud @ 2013-02-27 18:39 UTC (permalink / raw)
To: Bastien; +Cc: emacs-orgmode
Hi
>> * project
>> ** TODO headline :repeat:
>> a longer description of what the todo item is about
>> SCHEDULED: <2013-06-18 Tue +1m>
>
> The SCHEDULED line should be right after the headline, see the manual.
> It can sometimes work when it is on another line, but this is
> accidental, you should put the line right after the headline.
I just tried
* project
** TODO headline :repeat:
SCHEDULED: <2013-06-18 Tue +1m>
a longer description of what the todo item is about
but this will still add the state-changed-line between the SCHEDULED
line and the longer description (it will also add the property drawer
there, if it doesn't exist). If you track some daily changes this can
move the longer description away from the top quite fast, which is what
I would like to avoid.
Arun
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: logdone enhancement
2013-02-27 18:39 ` Arun Persaud
@ 2013-02-27 19:08 ` Nick Dokos
2013-02-27 20:09 ` Arun Persaud
0 siblings, 1 reply; 9+ messages in thread
From: Nick Dokos @ 2013-02-27 19:08 UTC (permalink / raw)
To: Arun Persaud; +Cc: Bastien, emacs-orgmode
Arun Persaud <apersaud@lbl.gov> wrote:
> Hi
>
> >> * project
> >> ** TODO headline :repeat:
> >> a longer description of what the todo item is about
> >> SCHEDULED: <2013-06-18 Tue +1m>
> >
> > The SCHEDULED line should be right after the headline, see the manual.
> > It can sometimes work when it is on another line, but this is
> > accidental, you should put the line right after the headline.
>
> I just tried
>
> * project
> ** TODO headline :repeat:
> SCHEDULED: <2013-06-18 Tue +1m>
> a longer description of what the todo item is about
>
> but this will still add the state-changed-line between the SCHEDULED
> line and the longer description (it will also add the property drawer
> there, if it doesn't exist). If you track some daily changes this can
> move the longer description away from the top quite fast, which is what
> I would like to avoid.
>
Isn't that what the LOGBOOK drawer is for? You put the mess in there, so
it's available when you open it, but you don't have to look at it most of
the time.
Nick
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: logdone enhancement
2013-02-27 19:08 ` Nick Dokos
@ 2013-02-27 20:09 ` Arun Persaud
0 siblings, 0 replies; 9+ messages in thread
From: Arun Persaud @ 2013-02-27 20:09 UTC (permalink / raw)
To: nicholas.dokos; +Cc: Bastien, emacs-orgmode
Hi
> Isn't that what the LOGBOOK drawer is for? You put the mess in there, so
> it's available when you open it, but you don't have to look at it most of
> the time.
nice! I didn't know about this one. This will solve my problem, although
I still would prefer that drawers, etc are added at the very end of the
entry and not before my additional description. But with LOGBOOK, I will
only have them separated by 3 lines (scheduled, logbook and properties)
which is not too bad.
Thanks for the tip!
Arun
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2013-02-27 20:10 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-02-27 6:21 logdone enhancement Arun Persaud
2013-02-27 8:33 ` Bastien
2013-02-27 9:15 ` Sebastien Vauban
2013-02-27 9:25 ` Bastien
2013-02-27 10:04 ` Sebastien Vauban
2013-02-27 12:22 ` Bastien
2013-02-27 18:39 ` Arun Persaud
2013-02-27 19:08 ` Nick Dokos
2013-02-27 20:09 ` Arun Persaud
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).