From mboxrd@z Thu Jan  1 00:00:00 1970
From: Robert Horn <rjhorn@alum.mit.edu>
Subject: Re: A proposed enhancement in entering timestamps
Date: Thu, 24 Mar 2016 11:30:18 -0400
Message-ID: <m3twjvvqph.fsf@alum.mit.edu>
References: <8760wlgw2t.fsf@mbork.pl> <874mc5gvnj.fsf@mbork.pl>
	<87fuvon48l.fsf@nicolasgoaziou.fr> <87twk4fiob.fsf@mbork.pl>
	<874mc3ewp4.fsf@nicolasgoaziou.fr> <87pourg252.fsf@mbork.pl>
	<8737ri1cla.fsf@mbork.pl> <87vb4cyqdp.fsf@nicolasgoaziou.fr>
	<87lh573oll.fsf@mbork.pl>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37625)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rjhorn@alum.mit.edu>) id 1aj7DN-0007Vm-Cy
	for emacs-orgmode@gnu.org; Thu, 24 Mar 2016 11:30:26 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rjhorn@alum.mit.edu>) id 1aj7DI-0006cG-ED
	for emacs-orgmode@gnu.org; Thu, 24 Mar 2016 11:30:25 -0400
Received: from mailbackend.panix.com ([166.84.1.89]:44730)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rjhorn@alum.mit.edu>) id 1aj7DI-0006cA-BP
	for emacs-orgmode@gnu.org; Thu, 24 Mar 2016 11:30:20 -0400
In-reply-to: <87lh573oll.fsf@mbork.pl>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Marcin Borkowski <mbork@mbork.pl>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>, Nicolas Goaziou <mail@nicolasgoaziou.fr>


>>> 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