From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Abrahams Subject: Re: Bug: "SCHEDULED: " positioning is fragile [7.8.06 (release_7.8.06.181.ga481)] Date: Fri, 06 Apr 2012 08:18:12 -0400 Message-ID: References: <871uo1l37g.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38902) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SG87V-00059k-WB for emacs-orgmode@gnu.org; Fri, 06 Apr 2012 08:18:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SG87N-0007Q7-P5 for emacs-orgmode@gnu.org; Fri, 06 Apr 2012 08:18:24 -0400 Received: from mail-qc0-f169.google.com ([209.85.216.169]:41656) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SG87N-0007PK-Kw for emacs-orgmode@gnu.org; Fri, 06 Apr 2012 08:18:17 -0400 Received: by qcsd16 with SMTP id d16so1587285qcs.0 for ; Fri, 06 Apr 2012 05:18:13 -0700 (PDT) In-Reply-To: <871uo1l37g.fsf@gnu.org> (Bastien's message of "Fri, 06 Apr 2012 09:38:43 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org on Fri Apr 06 2012, Bastien wrote: > Hi Dave, > > Dave Abrahams 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. 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. -- Dave Abrahams BoostPro Computing http://www.boostpro.com