From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Bug in org-time-stamp? Date: Fri, 5 Sep 2008 07:55:41 +0200 Message-ID: <1B7F5B7A-B3FB-45EE-9CB7-B22151A4C6BD@uva.nl> References: <33284510.1389.1220147808925.JavaMail.help@alum.mit.edu> Mime-Version: 1.0 (Apple Message framework v926) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KbVXo-0006Dh-Pv for emacs-orgmode@gnu.org; Fri, 05 Sep 2008 03:15:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KbVXn-0006Ck-G5 for emacs-orgmode@gnu.org; Fri, 05 Sep 2008 03:15:48 -0400 Received: from [199.232.76.173] (port=33785 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KbVXn-0006C8-2L for emacs-orgmode@gnu.org; Fri, 05 Sep 2008 03:15:47 -0400 Received: from mx20.gnu.org ([199.232.41.8]:39698) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KbVXm-0001QV-Oe for emacs-orgmode@gnu.org; Fri, 05 Sep 2008 03:15:46 -0400 Received: from ug-out-1314.google.com ([66.249.92.168]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KbVXl-0004B8-Po for emacs-orgmode@gnu.org; Fri, 05 Sep 2008 03:15:46 -0400 Received: by ug-out-1314.google.com with SMTP id a2so24879ugf.17 for ; Fri, 05 Sep 2008 00:15:45 -0700 (PDT) In-Reply-To: <33284510.1389.1220147808925.JavaMail.help@alum.mit.edu> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: bostjanv@alum.mit.edu Cc: bvilf@yahoo.com, emacs-orgmode@gnu.org Hi Bostjanv, first of all, I do not understand why you seem to think it matters if the mouse is inside or outside the time stamp when `C-c .' is called. I believe it does not matter at all. On Aug 31, 2008, at 3:56 AM, bostjanv@alum.mit.edu wrote: > 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. This is correct, and it is a bug in the documentation. The documentation shows how this function behaved a long time ago, but since then we decided that the current value of the timestamp should be the default instead as this application seems to be more common. This allows you, for example, to use this command to quickly change or add the time component of a stamp by typing 15:33 or so. If you want a shortcut to shift the time stamp to today, use "+0" at the prompt. Thank you for the report, I have updated the documentation to reflect the real behavior. - Carsten > > (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 > _______________________________________________ > 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