Re: [O] logdone enhancement
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
Re: [O] logdone enhancement
Arun Persaud 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
Re: [O] logdone enhancement
Hi Sébastien, "Sebastien Vauban" 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
Re: [O] logdone enhancement
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
Re: [O] logdone enhancement
Bastien, Bastien wrote: > Hi Sébastien, > > "Sebastien Vauban" > 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
Re: [O] logdone enhancement
Hi Sébastien, "Sebastien Vauban" 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
Re: [O] logdone enhancement
Hi Bastien, Bastien wrote: > Arun Persaud 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
Re: [O] logdone enhancement
Hi Arun, Arun Persaud 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
[O] logdone enhancement
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
