From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Bug: Extra space inserted in repeated tasks' date line
Date: Thu, 18 Aug 2011 22:54:04 +0200 [thread overview]
Message-ID: <80ei0iqw43.fsf@somewhere.org> (raw)
In-Reply-To: 87d3g2ofof.fsf@gnu.org
Hi Bastien,
Bastien wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>> ** This one won't be moved along with the heading
>> SCHEDULED: <2011-08-18 Thu>
>>
>> Because of this text here...
>
> This should be fixed now. "Meta" lines (SCHEDULED string, etc,
> along with the first properties drawer) will be indented correctly,
> even when text from the subtree start at the beginning of the line.
>
> Please confirm this works okay for you, and thanks for reporting
> this!
This works in many cases, but suffers some problems. Anyway, you're really not
far from giving this a definitive solution[1].
Here a compilation of cases which don't work, or work with an error being
generated in the echo area.
--8<---------------cut here---------------start------------->8---
* New section
The first one works, but generates an error ("setq: Wrong type argument:
number-or-marker-p, nil").
** The SCHED will be moved
SCHEDULED: <2011-08-18 Thu>
** This one now move as well along with the heading
SCHEDULED: <2011-08-18 Thu>
Even with this text here... but error is also generated.
Same for the following: works, with error.
** RDV client
DEADLINE: <2011-09-06 Tue 08:30-09:15>
** Feestje Iris
<2011-08-14 Sun 18:30>
Demoting this one does not move the active timestamp, but moves the SCHEDULED
line of the next entry.
** TODO Bi-weekly review
SCHEDULED: <2011-08-12 Fri ++14d>
:PROPERTIES:
:RESET_CHECK_BOXES: t:
:LAST_REPEAT: [2009-07-28 Tue 21:19]
:END:
Here, the properties aren't moved. The rest well.
--8<---------------cut here---------------end--------------->8---
Thank you so much for patching this. It will save me tens of minutes per
month, and an RSI because of adding them manually? ;-)
Best regards,
Seb
Footnotes:
[1] I've been sure for months that this worked before (like some half year
ago), but never tried on such a vintage version. Anyway, Carsten told me I
was wrong...
--
Sebastien Vauban
next prev parent reply other threads:[~2011-08-18 20:54 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
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 [this message]
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=80ei0iqw43.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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).