From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id oE3fMWq5xl6TDAAA0tVLHw (envelope-from ) for ; Thu, 21 May 2020 17:24:58 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id 2GVnLWq5xl7vJAAAB5/wlQ (envelope-from ) for ; Thu, 21 May 2020 17:24:58 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 66B97940253 for ; Thu, 21 May 2020 17:24:58 +0000 (UTC) Received: from localhost ([::1]:39914 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jbowC-0006aJ-V7 for larch@yhetil.org; Thu, 21 May 2020 13:24:56 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:50754) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jboO9-00070r-7k for emacs-orgmode@gnu.org; Thu, 21 May 2020 12:49:45 -0400 Received: from mail-qk1-x736.google.com ([2607:f8b0:4864:20::736]:33017) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jboO8-0007nC-9S for emacs-orgmode@gnu.org; Thu, 21 May 2020 12:49:44 -0400 Received: by mail-qk1-x736.google.com with SMTP id z80so7939213qka.0 for ; Thu, 21 May 2020 09:49:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:references:user-agent:from:to:cc:subject:in-reply-to :message-id:date:mime-version; bh=d5siCxKbOth8HFoQvjdWwkGpUHXARCbKiKEayRn4/rY=; b=Uton0M6w3XpE+gqQkIPHrEig+aX6LrHpkOu7clB+apjWZDeWNa3b5ewV72DxOiw8HK V8jf6Q+2cuTTlPT1wjoztxIJiWHcDOZWFD9zc1adjepAdjCszG/0NEdx/eeRsXkfVCHi af5HW6HzrvICotsu2W56kIh6V812QAsxD8PfucRayYn+ETWFcqqpQzZH8UctJ5fs2n1I dsdQ0YZB0vK0U/5hhkQkTG6SMLNeVb6wsdVhIxur5EBmycXJVo0XixZ/mpDE9z1R9FY5 0fHVE1n5IQNY1u1QgelmITcgEA72RJ877h5qvUzJd2o3OFUD2G5rMLaV4Q20erITL7VX /0WA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:references:user-agent:from:to:cc:subject :in-reply-to:message-id:date:mime-version; bh=d5siCxKbOth8HFoQvjdWwkGpUHXARCbKiKEayRn4/rY=; b=ji9whfCp+M3dW3F+c5uq9f9a/p9KXAb/02EfFpEVnivQSdeX0bVtiNFeo1S6nqKqZE Nboy5HsKmJKUD+DWiaS1X+j7e6hhU53IeiZHgQ8uZom1lTYOiJebq96oGDUP1lJyFJDE bAbOeJaEX5IGpcW+98FPuBTYerr1bcSgSjdR/WSJgpva+OQIt9HqtWL0zxds/YE9sEgG ++3LVbQfK2u0yC9gUG47Br0SZ+MeuD3Ul8yleAXjiUr5wTWzC6880yPhOO8O71GumcNC j4REytT9EzrRt9gOJCo6i0W8sKUrbS4jlhAb2NDLxf1lQR8GDU34nlxBrD9tEDwS5Zfd 172Q== X-Gm-Message-State: AOAM5320mR+AwJKinu24Qpf72SyCjDCCSWpVZUnwN63mzXgMOkL+WY+7 Qe3B4YrGbZuQMerm9cXH5foD8Kn/D/c= X-Google-Smtp-Source: ABdhPJw0WTS8dM5yA05Z/iakan3ljbGexQ5az9Slosc7BNgrmUx2hvAaY19csgC6qvaMCxLe9rDiWA== X-Received: by 2002:a37:a896:: with SMTP id r144mr10987731qke.251.1590079783023; Thu, 21 May 2020 09:49:43 -0700 (PDT) Received: from gusbrs-laptop ([193.37.252.119]) by smtp.gmail.com with ESMTPSA id v46sm5555278qth.77.2020.05.21.09.49.40 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Thu, 21 May 2020 09:49:42 -0700 (PDT) References: <875zcpqxnq.fsf@gmail.com> <87eerd78w7.fsf@ucl.ac.uk> <86d06xwaj2.fsf@panix.com> User-agent: mu4e 1.4.6; emacs 26.3 From: Gustavo Barros To: rjhorn@alum.mit.edu Subject: Re: A small idea to simplify (further) time input in the date/time prompt In-reply-to: <86d06xwaj2.fsf@panix.com> Message-ID: <87tv09p71a.fsf@gmail.com> Date: Thu, 21 May 2020 13:49:38 -0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed Received-SPF: pass client-ip=2607:f8b0:4864:20::736; envelope-from=gusbrs.2016@gmail.com; helo=mail-qk1-x736.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: emacs-orgmode@gnu.org, Eric S Fraga Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=fail (rsa verify failed) header.d=gmail.com header.s=20161025 header.b=Uton0M6w; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: 0.09 X-TUID: rMN8ZJnVjgRe Hi Robert, On Thu, May 21 2020, Robert Horn wrote: > Eric S Fraga writes: > >> On Thursday, 21 May 2020 at 09:29, Gustavo Barros wrote: >>> So I'd like to suggest a simplification there, which is: a string in >>> the format "hour h minute" (that's small caps letter "H"), but in >> >> I would be strongly in favour of having this option. This is how I >> write times in email messages, for instance, so would be more >> consistent >> for me. And especially when I communicate with my European partners >> when referring to times after 12 noon. >> > > I would be opposed. There are already dozens of different formats > used > in different situations and locations for writing the time. This > would > be yet another different time format. It is relatively unique in that > there is no other place in the world that uses it. I don't think that > uniqueness is an argument in its favor. > > There some other formats that are actually in widespread use worldwide > that I would prefer as available alternatives: > > European dot notation. Many people use the dot rather than the colon, > so 13:05 is written as 13.05. I think this is mostly a keyboard, pen, > and > pencil thing. Colon is harder to write. It's inconveniently located > on > many keyboards. The problem with dot notation is potential confusion > for more detailed time. "15:53:00.322348" is easy to guess and > understand. "15.53.00.322348" is more confusing. > > Military time, which is used in most militaries, aviation, etc. > > hhmmZ - Time in UTC on a 24-hr clock, also called "Zulu time". The > ISO 8601 time "11:21:00 -0400" would be 1521Z. This is almost > mandatory when dealing with multi-location scheduling so that > everyone > uses the same time base. > > hhmmJ or hhmmh - Time in local zone on a 24-hr clock. It's widely > used in military organizations for times that do not need > multi-location scheduling. The time "1121J" or "1121h" is usually > spoken in English as "eleven twenty one hours". These times are > also > lack the colon typing problem. > > I've not pushed for these mostly because convenience typing military > time isn't worth figuring out all the changes that would be needed. > > It's worth looking at all the issues discussed in ISO 8601 and > understanding them before you leap into time formatting changes. ISO > 8601 is a compromise solution with lots of warts, but it is widely > supported and understood. I do appreciate your arguments. But in reading them, I'd like to emphasize that I'm not in any way suggesting the timestamps be changed at all. The suggestion regards exclusively adding and extra way to input such times in the date/time prompt. And one which I feel is very much in the spirit of the prompt, which already takes ".", "+4d" (even just "+4"), "+2w", "+2tue" as valid date specifications. If I get this spirit correctly, it is to be smart in allowing short and easy input for the common cases, and the less common ones are handled by the full/formal date/time specification, which can always be inserted anyway. This kind of input simplification is already taken far for dates in the date/time prompt, but less so for time. And that's the only point my suggestion tries to address. I have no particular attachment for the "h" input form I suggested, except that it seemed natural (Eric's response seems to endorse it). If other ways to simplify input of time come up, they'd be equally appreciated, as far as I'm concerned. And if none come up, the current date/time prompt would still be my favorite tool for the task, of course. ;-) Best, Gustavo.