From: Gustavo Barros <email@example.com> To: Bastien <firstname.lastname@example.org> Cc: email@example.com Subject: Re: A small idea to simplify (further) time input in the date/time prompt Date: Tue, 02 Jun 2020 09:58:40 -0300 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Hi Bastien, On Tue, Jun 02 2020, Bastien wrote: > 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. Of course, there's absolutely no rush in this, and this is clearly not something to be added shortly before a release. Thank you very much for considering it. > Gustavo Barros <firstname.lastname@example.org> writes: > >> 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 > > All the above looks good to me as more flexible ways to input time. > > But: > >> 14h+1h -> 14:00-15:00 > > is not necessary. Instead, 14h+1 should produce 14:00-15:00. > > This way, the "+" in "[hour]+N" as the same meaning, whether [hour] is > formed as HH:MM or as Hh. > > Would you agree? I wasn't aware that a plain number after "+" in "[hour]+N" was interpreted as "N hours", I always went for a "3-4 digit plus colon" format to specify duration. But this is indeed a strong argument for things to work the same way for both kinds of input. Besides, I like the idea, but I'm probably missing something. In this case, how would you then input a duration smaller than an hour? Let's say 30 minutes? > Would you like to work on this change? I'm not sure I'm up for the task, but I would be willing to try. However, there's another problem. I can't offer signed papers for the foreseeable future. I'd love to, I've contacted FSF to do so last year, but my current employment terms imposed a barrier there, which I cannot circumvent. So I've been trying to contribute in the ways that I can, with ideas, reports, and so on. And I hope to be doing so with good ones. Anyway, if you, with your knowledge of the date/time prompt, think this sort of change might fit into a "tiny change" (even if it turns out it doesn't, ex-post), I'd be willing to give it a shot. But otherwise, I've got my hands tied. Thanks again. Best, Gustavo.
next prev parent reply other threads:[~2020-06-02 12:59 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 [this message] 2020-06-03 13:14 ` Gustavo Barros 2020-10-06 10:42 ` Gustavo Barros 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --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).