From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Bug: "SCHEDULED: " positioning is fragile [7.8.06 (release_7.8.06.181.ga481)] Date: Mon, 09 Apr 2012 17:05:37 +0200 Message-ID: <87pqbhgd32.fsf@gnu.org> References: <871uo1l37g.fsf@gnu.org> <877gxpyxs6.fsf@gnu.org> <878vi5xe7p.fsf@gnu.org> <87aa2lufe8.fsf@altern.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54792) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SHG8n-0000i3-9G for emacs-orgmode@gnu.org; Mon, 09 Apr 2012 11:04:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SHG8l-0001x7-Hh for emacs-orgmode@gnu.org; Mon, 09 Apr 2012 11:04:24 -0400 Received: from mail-wg0-f49.google.com ([74.125.82.49]:44778) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SHG8l-0001tc-8K for emacs-orgmode@gnu.org; Mon, 09 Apr 2012 11:04:23 -0400 Received: by wgbdr1 with SMTP id dr1so2993716wgb.30 for ; Mon, 09 Apr 2012 08:04:21 -0700 (PDT) In-Reply-To: (Dave Abrahams's message of "Mon, 09 Apr 2012 10:54:23 -0400") 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: Dave Abrahams Cc: emacs-orgmode@gnu.org, John Wiegley Hi Dave, Dave Abrahams writes: > I want the rule to be that you can have as much body text as you want > between the headline and the SCHEDULED: line. This won't happen. > Or failing that, I'd like > org's default keybindings to make it really hard to insert text between > the headline and SCHEDULED:. Any typing in that area should, by > default, force the point to jump after SCHEDULED: Yes, this is a possibility. The other possibility is to store SCHEDULED and DEADLINE information in a drawer. In both cases, this requires a careful discussion. As I cannot spend this time right now, the helper function to fix misformatted subtrees is better than nothing. And unless there is a Global Internet Strike (©) requesting this issue to be fixed, I think we should live with it -- or make a collective effort. > Thanks, I think... but I can't tell if everybody is missing my point. > I've been trying to argue for something that doesn't allow mistakes to > happen in the first place. I understand. But again: the mistake happens for people who move this line manually and for poeple who don't read the manual. Thanks for your understanding! -- Bastien