emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: bostjanv@alum.mit.edu
To: emacs-orgmode@gnu.org
Cc: bvilf@yahoo.com
Subject: Bug in org-time-stamp?
Date: Sat, 30 Aug 2008 21:56:48 -0400 (EDT)	[thread overview]
Message-ID: <33284510.1389.1220147808925.JavaMail.help@alum.mit.edu> (raw)

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

Section 8.2 (node: Creating timestamps) of the info manual contains the
following description:

`C-c .'
     Prompt for a date and insert a corresponding time stamp.  When the
     cursor is at a previously used time stamp, it is updated to NOW.
     When this command is used twice in succession, a time range is
     inserted.  

In my opinion, the second sentence does not correspond to the actual
operation. To see this, one can perform a test on a single-line org file,
for example:

* TODO <2008-08-28 Thu> test todo item

We encounter (at least) the following types of behavior:

(1) point is within the timestamp, mouse cursor is either inside or outside
    (if inside, do not click). In that case entering `C-c .' will result in
    a timestamp update query, and hitting RETURN will produce no change in
    the timestamp.
(2) point is outside the timestamp, mouse cursor inside. In that case the
    `C-c .' command and RETURN will result in an updated timestamp at the
    point position while the original timestamp remains unchanged.
(3) point is within the timestamp. If after `C-c .' and the timestamp query
    one clicks on a date in the calendar, then the original timestamp will
    be changed to the selected date.

On examining the first two cases one concludes that the origin of the problem
is quite simple: In Case (1) the default answer to the update query is the
ORIGINAL VALUE OF TIMESTAMP while in Case (2) it is NOW. In my opinion it
should be NOW in both cases. Case (3) does not require comment as the
corresponding behavior is expected.

Additionally, if the previously suggested change be accepted, I propose that
the above description in the info manual be changed to the following:
    
`C-c .'
     Prompt for a date and insert a corresponding time stamp.  When the
     point or mouse cursor is at a previously used time stamp, the prompt
     requests an updated value, and the latter is inserted at point
     (default is NOW). When this command is used twice in succession, a
     time range is inserted.  

Regards,
bostjanv

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

             reply	other threads:[~2008-08-31  1:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-31  1:56 bostjanv [this message]
2008-09-05  5:55 ` Bug in org-time-stamp? Carsten Dominik

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=33284510.1389.1220147808925.JavaMail.help@alum.mit.edu \
    --to=bostjanv@alum.mit.edu \
    --cc=bvilf@yahoo.com \
    --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).