From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: In org-mode 9 "Scheduled" and "Deadline" are no longer parsed if they are not in the beginning Date: Tue, 19 Jun 2018 16:44:46 +0200 Message-ID: <87muvqesyp.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46134) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fVHsK-0004JF-TK for emacs-orgmode@gnu.org; Tue, 19 Jun 2018 10:44:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fVHsH-0003el-OQ for emacs-orgmode@gnu.org; Tue, 19 Jun 2018 10:44:52 -0400 Received: from relay1-d.mail.gandi.net ([217.70.183.193]:48047) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fVHsH-0003dJ-GW for emacs-orgmode@gnu.org; Tue, 19 Jun 2018 10:44:49 -0400 In-Reply-To: (Igor Katson's message of "Tue, 19 Jun 2018 07:37:08 -0700") 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" To: Igor Katson Cc: emacs-orgmode@gnu.org Hello, Igor Katson writes: > I've been using org-mode for years, and somewhere between version 8 and 9, > a change happened, which I could not find in the changelogs. > > Here's how I often used to format TODO items which are scheduled: > > * TODO Item > some-text > some-more-text > SCHEDULED: <2018-06-19 Tue> > > In the newer versions of org, the SCHEDULED string is no longer parsed, and > I don't see it in agenda, unless I reformat it like this: > > * TODO Item > SCHEDULED: <2018-06-19 Tue> > some-text > some-more-text > > This broke the habit that I was using for years and also broke my existing > notes as I'm no longer able to see them in agenda. I wonder if this > behavior can be changed to work like before. No it cannot. SCHEDULED and DEADLINE must be in the line right below the heading. M-x org-lint will help you finding problematic lines. Not this is not really a change: most code in Org expected such lines to be located right below the heading since day 1. The agenda was a bit tolerant on that part. This is particularly important to make Org find information quickly. Regards, -- Nicolas Goaziou