From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Extra space inserted in repeated tasks' date line
Date: Thu, 18 Aug 2011 10:25:46 +0200 [thread overview]
Message-ID: <FEC2D818-E13F-4F4F-97BA-5189349D335C@gmail.com> (raw)
In-Reply-To: <80ei0jgmct.fsf@somewhere.org>
On Aug 18, 2011, at 10:22 AM, Sebastien Vauban wrote:
> Hi Bastien and Markus,
>
> Bastien wrote:
>> Markus Berlin <ecce.berlin@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
next prev parent reply other threads:[~2011-08-18 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 12:02 Bug: Extra space inserted in repeated tasks' date line Markus Berlin
2011-08-18 7:55 ` Bastien
2011-08-18 8:22 ` Sebastien Vauban
2011-08-18 8:25 ` Carsten Dominik [this message]
2011-08-18 9:04 ` Sebastien Vauban
2011-08-18 10:02 ` Carsten Dominik
2011-08-18 12:25 ` Sebastien Vauban
2011-08-18 16:19 ` Bastien
2011-08-18 20:54 ` Sebastien Vauban
2011-08-19 7:42 ` Bastien
2011-08-19 8:38 ` Sebastien Vauban
2011-08-19 8:45 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FEC2D818-E13F-4F4F-97BA-5189349D335C@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).