emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Charles Millar <millarc@verizon.net>
To: emacs-orgmode@gnu.org
Subject: Re: How to include time when generating timestamp for DEADLINE/SCHEDULE
Date: Fri, 13 Feb 2015 08:25:27 -0500	[thread overview]
Message-ID: <54DDFB47.50506@verizon.net> (raw)
In-Reply-To: <54DDF8BF.3040104@verizon.net>


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 
>> <yuri.niyazov@gmail.com> wrote:
>>> On Thu, Feb 12, 2015 at 4:16 PM, Subhan Michael Tindall
>>> <SubhanT@familycareinc.org> 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 date<space>time (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

  reply	other threads:[~2015-02-13 13:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 19:17 How to include time when generating timestamp for DEADLINE/SCHEDULE Subhan Michael Tindall
2015-02-12 20:44 ` Yuri Niyazov
2015-02-12 20:46 ` Dominic Surano
2015-02-12 23:16   ` Subhan Michael Tindall
2015-02-13  0:36     ` Yuri Niyazov
2015-02-13  0:37       ` Yuri Niyazov
2015-02-13 13:14         ` Charles Millar
2015-02-13 13:25           ` Charles Millar [this message]
2015-02-14 20:09             ` Yuri Niyazov

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=54DDFB47.50506@verizon.net \
    --to=millarc@verizon.net \
    --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).