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 16:51:59 +0200 Message-ID: <87aa2lufe8.fsf@altern.org> References: <871uo1l37g.fsf@gnu.org> <877gxpyxs6.fsf@gnu.org> <878vi5xe7p.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:40146) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SHFvb-0006AH-2f for emacs-orgmode@gnu.org; Mon, 09 Apr 2012 10:50:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SHFvZ-0006Rm-5b for emacs-orgmode@gnu.org; Mon, 09 Apr 2012 10:50:46 -0400 Received: from mail-wi0-f177.google.com ([209.85.212.177]:53446) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SHFvY-0006RW-RH for emacs-orgmode@gnu.org; Mon, 09 Apr 2012 10:50:45 -0400 Received: by wibhj13 with SMTP id hj13so1893974wib.12 for ; Mon, 09 Apr 2012 07:50:42 -0700 (PDT) In-Reply-To: (Dave Abrahams's message of "Mon, 09 Apr 2012 09:58:53 -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: > Sorry, but I don't want to spend the time on that. I'm trying to get > the rules changed so that it isn't so easy to corrupt an org file. The current rule is "Leave SCHEDULED: and DEADLINE: information where Org's `org-schedule' and `org-deadline' put it." Maybe I don't understand how do you want to change this rule. > I'm not much interested in building a tool to undo corruption. > >> FYI: Nicolas and I have been discussing about the issue you raised, and >> the integration of org-element.el will force us to be clearer about such >> cases, which is good. > > I sincerely hope that when you become clearer about such cases you pick > a liberal set of rules that isn't so error-prone. The ideas that I > can't just hit return after a headline and start typing a body, and that > I'll be nagged about misplaced SCHEDULED: lines, are both very > unappealing. I have just added this hack: "Check for misplaced SCHEDULED and DEADLINE cookies" http://orgmode.org/worg/org-hacks.html#sec-1-2-8 Here is the function: (defun org-check-misformatted-subtree () "Check misformatted entries in the current buffer." (interactive) (show-all) (org-map-entries (lambda () (move-beginning-of-line 2) (if (or (and (org-get-scheduled-time (point)) (not (looking-at (concat "^.*" org-scheduled-regexp)))) (and (org-get-deadline-time (point)) (not (looking-at (concat "^.*" org-deadline-regexp))))) (when (y-or-n-p "Fix this subtree? ") (message "Call the function again when you're done fixing this subtree.") (recursive-edit)) (message "All subtrees checked."))))) HTH, -- Bastien