From: Marcin Borkowski <mbork@mbork.pl>
To: Robert Horn <rjhorn@alum.mit.edu>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: A proposed enhancement in entering timestamps
Date: Thu, 24 Mar 2016 20:38:50 +0100 [thread overview]
Message-ID: <87k2kr3bud.fsf@mbork.pl> (raw)
In-Reply-To: <m3twjvvqph.fsf@alum.mit.edu>
On 2016-03-24, at 16:30, Robert Horn <rjhorn@alum.mit.edu> wrote:
>>>> On 2016-03-18, at 17:51, Marcin Borkowski <mbork@mbork.pl> wrote:
>>>>
>>>>> I'm now reading org-read-date-analyze to be able to enable US military
>>>>> format for hours (e.g., 2100 instead of 21:00). This is potentially
>>>>> very useful (at least for me), since I'll be able to enter the hour with
>
> This would be very convenient for me, but when it comes time to document
> it a more proper name is 24-hour notation. It's used by much more than
> the US military. It's standard for railway schedules in most of the
> world, medical records in most of the world, aviation worldwide, and
> other places.
Well, this seems not that obvious to me:
https://en.wikipedia.org/wiki/24-hour_clock#Description . It seems that
"24-hour notation" can also refer to the one with colon or full stop, so
it is ambiguous. But if anyone comes up with a better name than "US
military time", I'm all for it.
> I work mostly in 24-hr notation and putting that colon in the right
> place is mistake prone.
Not only that, but it is plain old inconvenient.
> R Horn
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
prev parent reply other threads:[~2016-03-24 19:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 11:52 A small fix in `org-read-date-analyze' Marcin Borkowski
2016-03-17 12:02 ` Marcin Borkowski
2016-03-17 22:12 ` Nicolas Goaziou
2016-03-18 5:40 ` Marcin Borkowski
2016-03-18 13:34 ` Nicolas Goaziou
2016-03-18 16:51 ` A proposed enhancement in entering timestamps (was: A small fix in `org-read-date-analyze') Marcin Borkowski
2016-03-18 19:02 ` A proposed enhancement in entering timestamps Samuel W. Flint
2016-03-18 20:26 ` Eric S Fraga
2016-03-22 20:28 ` A proposed enhancement in entering timestamps (was: A small fix in `org-read-date-analyze') Marcin Borkowski
2016-03-24 13:09 ` A proposed enhancement in entering timestamps Nicolas Goaziou
2016-03-24 15:03 ` Marcin Borkowski
2016-03-24 15:30 ` Robert Horn
2016-03-24 19:38 ` Marcin Borkowski [this message]
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=87k2kr3bud.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=rjhorn@alum.mit.edu \
/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).