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 16:00:45 -0500 Message-ID: <87k2nnspvm.fsf@pierrot.dokosmarshall.org> References: <87fuyctb8m.fsf@iki.fi> <87d1tgawij.fsf@alphaville.usersys.redhat.com> <87fuybq4ct.fsf@iki.fi> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50782) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aGYiy-0004PB-R1 for emacs-orgmode@gnu.org; Tue, 05 Jan 2016 16:01:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aGYiu-0001uV-Mp for emacs-orgmode@gnu.org; Tue, 05 Jan 2016 16:01:00 -0500 Received: from plane.gmane.org ([80.91.229.3]:53855) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aGYiu-0001tk-AQ for emacs-orgmode@gnu.org; Tue, 05 Jan 2016 16:00:56 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aGYis-0006Xx-BM for emacs-orgmode@gnu.org; Tue, 05 Jan 2016 22:00:54 +0100 Received: from pool-74-104-158-160.bstnma.fios.verizon.net ([74.104.158.160]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jan 2016 22:00:54 +0100 Received: from ndokos by pool-74-104-158-160.bstnma.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jan 2016 22:00:54 +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: > Nick Dokos writes: > >> Jarmo Hurri writes: >> >>> # ---------------------------------- >>> * 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? > > No it doesn't. What's happening...? Are you sure that you are using > _exactly_ the same timestamp I am using, with the time included in > addition to the date: > > <2016-01-07 Thu 15:00-16:15> > > So if you in this timestamp do "C-c ." followed by _nothing else_ than > "+1d", date switches to tomorrow? > As you guessed, I wasn't using your timestamp. The problem is that there is junk in the minibuffer already (the 15:00-16:15 part) and the cursor is left right after that without a space. I guess that causes parsing errors and the date is left unchanged unless you add the space manually (using the 8 spec, not the +1d spec - the latter does not change anything, but I haven't chased it through to see if it gets an error in parsing or there is something else going on). OTOH, doing a C-a and then entering either "8 " or "+1d " (the space is necessary to separate the days part from the hour:minutes part) works. The point is that the time part has to follow the date part. > A related thing: the documentation on timestamps says that "Org mode > will find whatever information is in there and derive anything you have > not specified from the default date and time. The default is usually the > current date and time, but when modifying an existing timestamp, or when > entering the second stamp of a range, it is taken from the stamp in the > buffer." So does this imply that "+1d" - if it would work - should > actually add one day to the given timestamp, not today? > Maybe. >>> 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. > > Nope, doesn't work here without the space, using the timestamp I wrote > above. I am in GNU Emacs 24.5.1, running the latest Org from git repo. > >>> 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. > > Ok, but it is actually a secondary - or tertiary - issue. > > Jarmo > > > -- Nick