On Aug 18, 2011, at 10:22 AM, Sebastien Vauban wrote: > Hi Bastien and Markus, > > Bastien wrote: >> Markus Berlin <ecce.ber...@googlemail.com> writes: >> >>> some time ago I noticed this small bug (small but it keeps annoying me!): >>> >>> If the following are set: >>> >>> (setq org-log-done 'time) >>> (setq org-log-repeat nil) >>> >>> then if you press C-c C-t on a repeated tasks, like this one: >>> >>> * TODO do nothing >>> SCHEDULED: <2011-08-12 Fr .+2d> >>> >>> an extra space is introduced just before "SCHEDULED", i.e. you get: >>> >>> * TODO do nothing >>> SCHEDULED: <2011-08-17 Mi .+2d> >>> ^ >>> >>> instead of what you want: >>> >>> * TODO do nothing >>> SCHEDULED: <2011-08-17 Mi .+2d> >> >> This is fixed in the current git repo -- please test and confirm. > > Similar to this, I've noticed that sometimes the SCHEDULED line (or DEADLINE, > or ...) is moved synchronously with the heading when promoting/demoting, > sometimes not. > > I now found in which cases it does and when it does not: it depends on the > presence of text in the entry.
It depends on the presence of *unindented* text in the entry, and purposefully so. See the variable `org-adapt-indentation'. HTH - Carsten > > So, for example: > > --8<---------------cut here---------------start------------->8--- > * The SCHED will be moved > SCHEDULED: <2011-08-18 Thu> > > * This one won't be moved along with the heading > SCHEDULED: <2011-08-18 Thu> > > Because of this text here... > --8<---------------cut here---------------end--------------->8--- > > becomes, when demoted: > > --8<---------------cut here---------------start------------->8--- > * New section > > ** The SCHED will be moved > SCHEDULED: <2011-08-18 Thu> > > ** This one won't be moved along with the heading > SCHEDULED: <2011-08-18 Thu> > > Because of this text here... > --8<---------------cut here---------------end--------------->8--- > > Best regards, > Seb > > -- > Sebastien Vauban > > - Carsten
