emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: How exactly does "C-c ." work in an existing timestamp?
Date: Tue, 05 Jan 2016 15:19:21 +0200	[thread overview]
Message-ID: <87fuyctb8m.fsf@iki.fi> (raw)

[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]


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.

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.

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.")

How exactly does modifying the timestamp with "C-c ." work? I know it is
possible to modify the timestamp with other commands, such as S-up, but
I like the idea of modifying it with "C-c .", because the latter shows
the calendar automatically.

Thanks for help in advance,

Jarmo


[-- Attachment #2: screenshot --]
[-- Type: image/jpeg, Size: 31315 bytes --]

             reply	other threads:[~2016-01-05 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 13:19 Jarmo Hurri [this message]
2016-01-05 15:14 ` How exactly does "C-c ." work in an existing timestamp? Nick Dokos
2016-01-05 18:16   ` Jarmo Hurri
2016-01-05 21:00     ` Nick Dokos

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=87fuyctb8m.fsf@iki.fi \
    --to=jarmo.hurri@iki.fi \
    --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).