From mboxrd@z Thu Jan 1 00:00:00 1970 From: Charles Millar Subject: Re: How to include time when generating timestamp for DEADLINE/SCHEDULE Date: Fri, 13 Feb 2015 08:25:27 -0500 Message-ID: <54DDFB47.50506@verizon.net> References: <8e8765aacd3d4148986e0834917c3596@fcmailsvr3.familycareinc.org> <54DDF8BF.3040104@verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38804) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMGE2-0003ZO-W9 for emacs-orgmode@gnu.org; Fri, 13 Feb 2015 08:24:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YMGDy-0002U4-PS for emacs-orgmode@gnu.org; Fri, 13 Feb 2015 08:24:06 -0500 Received: from vms173001pub.verizon.net ([206.46.173.1]:41776) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMGDy-0002Tr-LI for emacs-orgmode@gnu.org; Fri, 13 Feb 2015 08:24:02 -0500 Received: from [192.168.1.4] ([96.238.154.15]) by vms173001.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0NJP00D0UP7LW890@vms173001.mailsrvcs.net> for emacs-orgmode@gnu.org; Fri, 13 Feb 2015 07:23:47 -0600 (CST) In-reply-to: <54DDF8BF.3040104@verizon.net> 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 On 02/13/2015 08:14 AM, Charles Millar wrote: > > On 02/12/2015 07:37 PM, Yuri Niyazov wrote: >> PS It is clear that you can *both* select the correct date using >> calendar, and *then* type in the time while still in the calendar >> selector, right? >> >> On Thu, Feb 12, 2015 at 5:36 PM, Yuri Niyazov >> wrote: >>> On Thu, Feb 12, 2015 at 4:16 PM, Subhan Michael Tindall >>> wrote: >>>> Not really an acceptable answer. Having to use 2 different >>>> interface methods to fill in one time/date stamp value is confusing >>>> and cludgy. Plus, if you type in a full time/date stamp + time, you >>>> can still move around in the calendar, but it doesn't update the >>>> selected datestamp in yellow. Also confusing. >>> Cludgy is in the eye of the beholder. I am hugely bothered by various >>> inconsistencies in org-mode user interface (see my other posts to this >>> list) but this one is very far down on the list. This is why: >>> >>> When I need to schedule a date, it is sufficiently close to today's >>> date that it is usually 2-3 S+ARROWS keystrokes away from today, so >>> the calendar with "today" selected as default is great. >>> >>> So, let's see how a time selector would work: >>> >>> When you bring up a time selector, it could by default show one of the >>> following three options: >>> >>> 1) The current time >>> 2) The last time you selected when you used the time selector >>> 3) Some default configurable time like "noon" >>> >>> When I need to schedule a time for an event, the time that something >>> needs to happen is usually not related to any times on that list, so >>> using S+ARROWS would be less efficient than typing out the time, which >>> is at most four keystrokes if its on the hour. (E.g. "10pm" ). Of >>> course, this is only true if you are a touch-typist. >>> > > Why bother with the arrow keys at all? I have a capture template for > appointments and deadlines which requests date and time. Calendar is > called. Rather than arrow keys I type the datetime (optional > duration) and then enter - e.g. call the template, then "2/28 13:30 > (and then enter the rest of template requests such as 'What has to be > done"" > > Charlie Millar Forgot to mention that with the deadline I also might enter a lead time