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: Mon, 09 Apr 2012 11:52:33 -0400 Message-ID: References: <871uo1l37g.fsf@gnu.org> <877gxpyxs6.fsf@gnu.org> <878vi5xe7p.fsf@gnu.org> <87aa2lufe8.fsf@altern.org> <87pqbhgd32.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:53625) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SHGtT-0000le-OW for emacs-orgmode@gnu.org; Mon, 09 Apr 2012 11:52:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SHGtR-00081D-NQ for emacs-orgmode@gnu.org; Mon, 09 Apr 2012 11:52:39 -0400 Received: from mail-qc0-f169.google.com ([209.85.216.169]:59149) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SHGtR-00080v-JN for emacs-orgmode@gnu.org; Mon, 09 Apr 2012 11:52:37 -0400 Received: by qcsd16 with SMTP id d16so2882655qcs.0 for ; Mon, 09 Apr 2012 08:52:35 -0700 (PDT) In-Reply-To: <87pqbhgd32.fsf@gnu.org> (Bastien's message of "Mon, 09 Apr 2012 17:05:37 +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, John Wiegley on Mon Apr 09 2012, Bastien wrote: > 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.=20=20 > > This won't happen.=20=20 Because...? >> 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. That would be an "easy" solution. > 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.=20=20 Yes. > And unless there is a Global Internet Strike (=C2=A9) requesting this iss= ue > to be fixed, I think we should live with it -- or make a collective > effort. I understand. >> 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. And again: this is a developer-centric response. As a matter of usability it doesn't matter very much that "you told me so" (in a manual 100s of pages long --- and it's buried in a footnote, for chrissake!) when the mistake is trivially easy to make... and it is. I only have only ever "moved that line" without knowing I was doing it. --=20 Dave Abrahams BoostPro Computing http://www.boostpro.com