emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Olivier Berger <olivier.berger@telecom-sudparis.eu>
To: emacs-orgmode@gnu.org
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	[thread overview]
Message-ID: <87fumtugbc.fsf_-_@inf-11879.int-evry.fr> (raw)
In-Reply-To: 84twb9ypor.fsf@gmail.com

Hi.

Marco Wahl <marcowahlsoft@gmail.com> 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)

  reply	other threads:[~2016-11-15 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15  9:55 Compact schedule time ranges no longer supported in agenda in org 9 ? Olivier Berger
2016-11-15 10:59 ` Marco Wahl
2016-11-15 11:35   ` Olivier Berger [this message]
2016-11-15 12:53     ` SCHEDULED: now needs to be on 2nd line ? - Was: " Marco Wahl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fumtugbc.fsf_-_@inf-11879.int-evry.fr \
    --to=olivier.berger@telecom-sudparis.eu \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).