From: Gustavo Barros <email@example.com> To: Bastien <firstname.lastname@example.org> Cc: email@example.com Subject: Re: [Feature Request] More flexibility in org-speed-commands customization Date: Sat, 01 May 2021 18:24:14 -0300 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Hi Bastien, On Sat, 01 May 2021 at 13:24, Bastien <firstname.lastname@example.org> wrote: > Hi Gustavo, > > Gustavo Barros <email@example.com> writes: > >> I don't know if there is a strong reason to hard-code the set of keys >> in `org-speed-commands-default'. But, if there isn't, could you >> consider (somehow) exposing the whole set of `org-speed-commands' to >> user customization? > > Well, no, I don't see a strong reason to hard-code the set of speedy > keys. See the attached patch, which proposes to use just one option > `org-speed-commands'. > > This would be a breaking change, but I don't think we do otherwise. > > Would this suit your needs? What do you think about the change? Thank you for seeing to this. Yes, the patch corresponds pretty much to what I had in mind. That's the way I'd go there too. And it's not about my needs here, I can verify it is safe to override the defconst and do so (as indeed I do). I was thinking more of that kind of user which would be uncertain if they could, and might eventually refrain from using a nice feature for framing it an "expert kind of stuff". A possible way to mitigate breakage here can be at hand, since we ended up with a third name (a proper one, btw). You could mark `org-speed-commands-user' as obsolete but keep it, for the due time as usual, and append it to `org-speed-commands' somehow (no need to distinguish them in `org-speed-command-help' though). Those who had overriden `org-speed-commands-default' are on their own, of course, as they shouldn't have done that in the first place. ;-) Best regards, Gustavo.
next prev parent reply other threads:[~2021-05-01 21:24 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-03 18:49 Gustavo Barros 2020-08-17 9:40 ` Marco Wahl 2020-08-17 10:39 ` Gustavo Barros 2020-09-04 17:45 ` Bastien 2020-09-04 18:37 ` Gustavo Barros 2021-05-01 16:24 ` Bastien 2021-05-01 21:24 ` Gustavo Barros [this message] 2021-05-02 6:29 ` Bastien 2021-05-02 16:03 ` Gustavo Barros
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: [Feature Request] More flexibility in org-speed-commands customization' \ /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).