From: Robert Horn <rjhorn@alum.mit.edu>
To: Marcin Borkowski <mbork@mbork.pl>
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 11:30:18 -0400 [thread overview]
Message-ID: <m3twjvvqph.fsf@alum.mit.edu> (raw)
In-Reply-To: <87lh573oll.fsf@mbork.pl>
>>> 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.
I work mostly in 24-hr notation and putting that colon in the right
place is mistake prone.
R Horn
next prev parent reply other threads:[~2016-03-24 15:30 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 [this message]
2016-03-24 19:38 ` Marcin Borkowski
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3twjvvqph.fsf@alum.mit.edu \
--to=rjhorn@alum.mit.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=mbork@mbork.pl \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.