From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id +K3bBTdb1l4MLQAA0tVLHw (envelope-from ) for ; Tue, 02 Jun 2020 13:59:19 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id AGmkATdb1l7/KQAAbx9fmQ (envelope-from ) for ; Tue, 02 Jun 2020 13:59:19 +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 5BAE19401AE for ; Tue, 2 Jun 2020 13:59:18 +0000 (UTC) Received: from localhost ([::1]:54242 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jg7Rl-0008VN-Ad for larch@yhetil.org; Tue, 02 Jun 2020 09:59:17 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:35446) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jg7RS-0008V4-9M for emacs-orgmode@gnu.org; Tue, 02 Jun 2020 09:58:58 -0400 Received: from [183.249.132.153] (port=1997 helo=localhost) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jg7RR-0001JF-3d for emacs-orgmode@gnu.org; Tue, 02 Jun 2020 09:58:57 -0400 Received: by localhost (Postfix, from userid 1000) id AF74624153A; Tue, 2 Jun 2020 21:58:52 +0800 (CST) References: <875zcpqxnq.fsf@gmail.com> User-agent: mu4e 1.4; emacs 28.0.50 From: stardiviner To: Gustavo Barros Subject: Re: A small idea to simplify (further) time input in the date/time prompt In-reply-to: <875zcpqxnq.fsf@gmail.com> Date: Tue, 02 Jun 2020 21:58:52 +0800 Message-ID: <87k10pbmcj.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-Host-Lookup-Failed: Reverse DNS lookup failed for 183.249.132.153 (deferred) Received-SPF: softfail client-ip=183.249.132.153; envelope-from=numbchild@gmail.com; helo=localhost X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/02 09:55:46 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: 53 X-Spam_score: 5.3 X-Spam_bar: +++++ X-Spam_report: (5.3 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, FSL_HELO_NON_FQDN_1=0.001, HELO_LOCALHOST=3.828, NML_ADSP_CUSTOM_MED=0.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: reject 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: , Reply-To: numbchild@gmail.com Cc: emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" 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: 1.59 X-TUID: ZB7Kicjwrjwe =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Gustavo Barros writes: > Hi All, > > the Org date/time prompt does deliver the promise in the manual that we "= start > getting annoyed by pretty > much any other way of entering a date/time out there". It has indeed bec= ome so > for me, as the date/time prompt is very neat. But there is one place whe= re > input could be even shorter, which is time input. > > Currently, time input mostly requires "hour colon minutes", thus a full t= ime > specification even when minutes are "00". And "mostly" because you can g= et away > with that last part if you use am/pm convention (alas, I do not belong to= those > strange corners of the world). Besides, the colon is a shift-key in many= common > keyboard layouts (from a simple search, it seems to be so in British, Ame= rican, > US International, German, Spanish, and Portuguese layouts, it doesn't see= m to be > so for the French layout though). > > 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 which "hour h" wou= ld also > be recognized as a full hour and "00" minutes presumed. The mnemonic is = obvious > for "hour", which works well for English, French, Spanish, Portuguese, no= t so > much for German. > > With this, we'd have some example inputs, and their respective results: > > 8h -> 08:00 > 10h30 -> 10:30 > 18h -> 18:00 > 9h-10h -> 09:00-10:00 > 9h30-10h -> 09:30-10:00 > 14h+1h -> 14:00-15:00 > Which date/time prompt do you mean? Like set schedule or deadline? If just = raw timestamp, it makes me confused whether it is time continuance. > This would ease input in two ways. First, it presumes the minutes in full > hours, thus dispensing with this typing. Considering full hours are a ve= ry > common case for scheduling and appointments, that shortening should be > significant. It is also one key shorter than the am/pm way for full hour= s, and > two keys shorter for non full hours in the same case. Second, it is easi= er to > type "h" than it is to type ":", it is easier to reach and it is not a > shift-key, so the chord is gone too. > > One corner case which will arise is if "zero hour" should also be presume= d. > Arguably midnight is not that common in most people's agenda, and could be > either "0h" or "24h", so we should not really worry in shortening somethi= ng like > "midnight and thirty minutes" as "h30". But this is more tricky with dur= ation > specification, that is with "+". In this case minutes not comprising a f= ull > hour might well be common. So, how to specify an appointment starting at= 10:00 > that lasts 30 minutes? Some alternatives could be: "10h+0h30", "10h+h30", > "10h+30m". On a first thought I like the last one better, but I'm really= not > sure what the best approach should be here. > > Needless to say, current input conventions should not change. This is ju= st > thought as an additional way of inputting time, alongside the ones which = already > exist. I'm unaware of any use of "h" in the date/time prompt (or of "m",= for > that matter), so I presume this should be viable without conflicting with= other > currently recognized input forms. > > > That's the small suggestion I had to make for the date/time prompt. I gu= ess, > technically, this should be filed as "feature request". But it is just a= n idea > I bring to your consideration, in the hope someone else here also likes i= t. > > > Best, > Gustavo. =2D --=20 [ stardiviner ] I try to make every word tell the meaning that I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3 =2D----BEGIN PGP SIGNATURE----- iQFIBAEBCAAyFiEE8J9lDX1nSBmJJZFAG13xyVromsMFAl7WWxwUHG51bWJjaGls ZEBnbWFpbC5jb20ACgkQG13xyVromsOi4Qf/RpkotaYxjmrDA+SsjqK4ep7sLM+Y tLwm+N47cYYDGPNR3M9o9WZYNxLncygdxXF2eYQjX7DQHmuZ8rLLyNa3Yb9P7vUb OYywOyTWgSa5wgp1cOJepcFS384DZvZeSg+odhrJDr5wPfhfN7NpbhB3VB3TLiEr hIHx1XzBfZbNifMR90gupPIZt2IEfHqcoI7zGa1uHfoDRPYDU61m2cVj4ZZDc1Ya H8gPAFQD+oGbg32PUw6vQn4a6x7Qk668G0kP52e5yCISG8S5P7BKrk0HSKClPUxM GjH0kYVm5DzEOm6YQvnWfGr2EIDuHLlMxvBaxyIXmMYc+k61RBAisKS1WA=3D=3D =3DQSbI =2D----END PGP SIGNATURE-----