From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier Berger Subject: SCHEDULED: now needs to be on 2nd line ? - Was: Re: Compact schedule time ranges no longer supported in agenda in org 9 ? Date: Tue, 15 Nov 2016 12:35:03 +0100 Message-ID: <87fumtugbc.fsf_-_@inf-11879.int-evry.fr> References: <8760npnk38.fsf@inf-11879.int-evry.fr> <84twb9ypor.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51582) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c6c1x-0002gG-4R for emacs-orgmode@gnu.org; Tue, 15 Nov 2016 06:36:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c6c1t-000172-OY for emacs-orgmode@gnu.org; Tue, 15 Nov 2016 06:36:01 -0500 Received: from [195.159.176.226] (port=59942 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c6c1t-00016C-I6 for emacs-orgmode@gnu.org; Tue, 15 Nov 2016 06:35:57 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1c6c1S-00011D-VW for emacs-orgmode@gnu.org; Tue, 15 Nov 2016 12:35:30 +0100 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: emacs-orgmode@gnu.org Hi. Marco Wahl writes: > >> For long I've been using a compact form for defining scheduled tasks >> with a time range/interval as : >> >> SCHEDULED: <2016-11-14 lun. 14:00-15:00> >> >> instead of : >> >> SCHEDULED: <2016-11-14 lun. 14:00>--<2016-11-14 lun. 15:00> >> >> It seems this no longer works in org 9 as the tasks don't appear any >> more in the agenda views. >> > I can not confirm your statement. > > E.g. the entry > > * Meeting > SCHEDULED: <2016-11-15 Tue 14:00-15:00> > > in an agenda file tmp.org appears in my agenda as > > tmp: 14:00-15:00 Scheduled: Meeting > > Maybe you can check again and provide a CME? > You're right, that still works. However, the issue is that the SCHEDULED: indication now needs to be placed on the second line right after the entry's headline, whereas it used to be recognized even in later lines before org 9... So : ** TODO meeting something SCHEDULED <2016-11-15 Tue 14:00-15:00> won't work, but : ** TODO meeting SCHEDULED <2016-11-15 Tue 14:00-15:00> something works. Bug, feature ? Thanks in advance. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France)