From: Gustavo Barros <firstname.lastname@example.org> To: Bastien <email@example.com> Cc: firstname.lastname@example.org Subject: Re: A small idea to simplify (further) time input in the date/time prompt Date: Tue, 06 Oct 2020 07:42:13 -0300 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi All, Hi Bastien, if I may kindly bump this patch for review. Best regards, Gustavo. On Wed, 03 Jun 2020 at 10:14, Gustavo Barros <email@example.com> wrote: > Hi Bastien, > > On Tue, Jun 02 2020, Bastien wrote: > >> Hi Gustavo, >> >> I like this idea, thanks for proposing it. We are in feature freeze >> for core features, so we have time to work on this for Org 9.5. >> > > [...] > >> Would you agree? Would you like to work on this change? > > Well, I did give it a shot. And, as it turns out, this might be > manageable within my limitations. > > A preliminary patch is attached, for comments. > > I took here the stance of following the same treatment which is given > to > am/pm times, and of using the letter "h" as sole main identifier. In > particular, standard "HH:MM" times take precedence, as is the case for > am/pm times. And duration specification with numbers only are > presumed > to be hours, which was already the case, the patch does not introduce > any changes here. The input will match for this format for "number h > 2-digit-number", where either the hour or the minutes, but not both, > can > be omitted and, if so, is presumed to be zero. 24h format is also > presumed. > > With it, some example inputs/outputs for time in the date/time prompt: > > | input | output | > |-----------+-------------| > | 9h | 09:00 | > | h45 | 00:45 | > | 21h | 21:00 | > | 9h-10h | 09:00-10:00 | > | 9h--10h30 | 09:00-10:30 | > | 18h30+h30 | 18:30-19:00 | > | 18h30+1 | 18:30-19:30 | > | 18h30+1h | 18:30-19:30 | > > And some sanity checks: > > | input | output | Observation > | > |-----------+----------------------+-------------------------------------------| > | 10:00 9h | 10:00 | by design, as for am/pm times > | > | 10am 9h | 10:00 | expected from coming after am/pm > handling | > | 10:00-11h | 10:00-11:00 | > | > | 10h-11:00 | no match | am/pm also does not match here > | > | +9h | no match | > | > | -9h | no match | > | > | h | no match | > | > | 10h+h | no match | > | > | h5 | no match | > | > | 10h70 | no match | > | > | 29h | 2020-06-04 Thu 05:00 | makes sense, same as for 29:00 > | > | 30h | no match | as per the regexp > | > > WDYT? > > Best, > Gustavo.
next prev parent reply other threads:[~2020-10-06 10:43 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-21 12:29 Gustavo Barros 2020-05-21 12:44 ` Gustavo Barros 2020-05-21 12:46 ` Eric S Fraga 2020-05-21 15:52 ` Robert Horn 2020-05-21 16:46 ` Detlef Steuer 2020-05-21 16:49 ` Gustavo Barros 2020-05-21 20:09 ` Robert Horn 2020-06-02 12:08 ` Bastien 2020-06-02 12:58 ` Gustavo Barros 2020-06-03 13:14 ` Gustavo Barros 2020-10-06 10:42 ` Gustavo Barros [this message] 2021-05-01 15:40 ` Bastien 2021-05-01 20:15 ` Gustavo Barros 2020-06-02 13:58 ` stardiviner 2020-06-02 14:14 ` Gustavo Barros 2020-06-02 14:42 ` stardiviner
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: A small idea to simplify (further) time input in the date/time prompt' \ /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
Code repositories for project(s) associated with this 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).