From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: How exactly does "C-c ." work in an existing timestamp? Date: Tue, 05 Jan 2016 10:14:44 -0500 Message-ID: <87d1tgawij.fsf@alphaville.usersys.redhat.com> References: <87fuyctb8m.fsf@iki.fi> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36823) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aGTK9-0007ZT-OS for emacs-orgmode@gnu.org; Tue, 05 Jan 2016 10:15:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aGTK6-0007qA-HK for emacs-orgmode@gnu.org; Tue, 05 Jan 2016 10:15:01 -0500 Received: from plane.gmane.org ([80.91.229.3]:55766) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aGTK6-0007q4-A7 for emacs-orgmode@gnu.org; Tue, 05 Jan 2016 10:14:58 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aGTK1-00046v-DR for emacs-orgmode@gnu.org; Tue, 05 Jan 2016 16:14:53 +0100 Received: from nat-pool-bos-t.redhat.com ([66.187.233.206]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jan 2016 16:14:53 +0100 Received: from ndokos by nat-pool-bos-t.redhat.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jan 2016 16:14:53 +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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Jarmo Hurri writes: > Greetings. > > Consider the following org file > > # ---------------------------------- > * testing > <2016-01-07 Thu 15:00-16:15> > # ---------------------------------- > > When I move my cursor inside the timestamp and press "C-c .", control > jumps to a minibuffer in the echo area. But when I try, in the echo > area, to modify the date in the timestamp, it gets a bit weird to me. > > 1. If I try to use the method specified in the documentation to bump the > date one day forward by typing +1d, nothing sensible happens. It > doesn't matter if I type "+1d" directly, or " +1d" with a leading > space. > That's relative to *today*, not relative to the existing timestamp. +1d changes it to tomorrow. Does that not work for you? > 2. If I type " 8" (note leading space), the date will move to the 8th, > that is, forward by one day. But a leading space is required. > Not here - with or without space, it changes it to next Friday 2016-01-08. > 3. If I move my cursor on top of the current date, still in the echo > area, the start time of the meeting and the duration start jumping > forward in the echo area. Please find attached a screenshot of what > the situation looks like. (This at least looks like a bug, or a > "feature.") Yes, that's weird - not sure what causes this. -- Nick