From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manuel Koell Subject: Org assumes scheduled/deadline time from headline Date: Fri, 17 Jul 2015 12:25:10 +0200 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11425bd04ac984051b0f9a30 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41126) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZG2pN-0004OG-8K for emacs-orgmode@gnu.org; Fri, 17 Jul 2015 06:25:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZG2pM-0001OB-B0 for emacs-orgmode@gnu.org; Fri, 17 Jul 2015 06:25:13 -0400 Received: from mail-ig0-x235.google.com ([2607:f8b0:4001:c05::235]:36929) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZG2pM-0001Nv-53 for emacs-orgmode@gnu.org; Fri, 17 Jul 2015 06:25:12 -0400 Received: by igbpg9 with SMTP id pg9so33696459igb.0 for ; Fri, 17 Jul 2015 03:25:10 -0700 (PDT) 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: emacs-orgmode@gnu.org --001a11425bd04ac984051b0f9a30 Content-Type: text/plain; charset=UTF-8 I'm using the org-journal extension from Bastian Berchtold to write my daily stuff down. Some of my journal entries (headlines) start with a time like 12:17 or 20:33. When I make a TODO out of it and set a schedule/deadline date, orgmode assumes the time for the schedule/deadline date from the headline. How can I prevent this (wrong) behaviour? I guess it is a feature rather than a bug... --001a11425bd04ac984051b0f9a30 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm using the org-journal extension from Bastian Berch= told to write my daily stuff down. Some of my journal entries (headlines) s= tart with a time like 12:17 or 20:33. When I make a TODO out of it and set = a schedule/deadline date, orgmode assumes the time for the schedule/deadlin= e date from the headline. How can I prevent this (wrong) behaviour? I guess= it is a feature rather than a bug...
--001a11425bd04ac984051b0f9a30--