emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@gnu.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: "SCHEDULED: " positioning is fragile [7.8.06 (release_7.8.06.181.ga481)]
Date: Mon, 09 Apr 2012 13:01:13 +0200	[thread overview]
Message-ID: <877gxpyxs6.fsf@gnu.org> (raw)
In-Reply-To: <m2d37lgikb.fsf@boostpro.com> (Dave Abrahams's message of "Fri, 06 Apr 2012 08:18:12 -0400")

Dave Abrahams <dave@boostpro.com> writes:

>>> Given the following:
>>>
>>> * TODO Some headline
>>> SCHEDULED: <2012-04-05 Thu>
>>>
>>> If I add body text between the headline and the SCHEDULED: line, some
>>> things work, but others don't.  
>>
>> See this footnote in the section "8.3.1 Inserting deadlines or
>> schedules" of the manual:
>>
>>    (1) The `SCHEDULED' and `DEADLINE' dates are inserted on the line
>> right below the headline.  Don't put any text between this line and the
>> headline.
>
> That doesn't make it right.  

No, but it makes it clear that users should put SCHEDULED: <...> lines
right after the headline.  

> This is a serious usability bug and a newbie trap.
>
> As I mentioned in my report, if some of the commands can handle it,
> there's no reason all of them shouldn't handle it.  

> The only other valid interpretation is that those commands that are
> handling it as I expect are broken and they're changing things that
> should really be treated as body text and just happen to look like a
> SCHEDULED line.

Patch welcome.

Or even more useful: write a small function that goes an Org buffer 
and spot misformatted subtrees, offering to fix them interactively.
Can you write this?

Thanks,

-- 
 Bastien

next prev parent reply	other threads:[~2012-04-09 11:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 14:41 Bug: "SCHEDULED: " positioning is fragile [7.8.06 (release_7.8.06.181.ga481)] Dave Abrahams
2012-04-06  7:38 ` Bastien
2012-04-06 12:18   ` Dave Abrahams
2012-04-09 11:01     ` Bastien [this message]
2012-04-09 11:20       ` Dave Abrahams
2012-04-09 12:49         ` Bastien
2012-04-09 13:58           ` Dave Abrahams
2012-04-09 14:51             ` Bastien
2012-04-09 14:54               ` Dave Abrahams
2012-04-09 15:05                 ` Bastien
2012-04-09 15:52                   ` Dave Abrahams
2012-04-10 13:43               ` Rainer Stengele
2012-04-10 14:12                 ` Bastien
2012-04-09 20:24           ` John Wiegley
2012-04-10 12:13   ` [PATCH] " Jérémie Courrèges-Anglas
2012-04-10 12:34     ` Bastien
2012-04-10 13:34       ` Jérémie Courrèges-Anglas
2012-04-10 13:40         ` 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=877gxpyxs6.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=dave@boostpro.com \
    --cc=emacs-orgmode@gnu.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

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).