From: "Juan Manuel Macías" <email@example.com> To: Ihor Radchenko <firstname.lastname@example.org> Cc: orgmode <email@example.com> Subject: Re: [PATCH] speed commands: error message when a key is not associated with a command Date: Sun, 01 May 2022 11:00:02 +0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <877d757vg3.fsf@localhost> (Ihor Radchenko's message of "Sun, 01 May 2022 12:01:16 +0800") Ihor Radchenko writes: > This would not solve the problem of shadowing. > It may be better idea to provide a custom variable controlling > org-babel-speed-command-activate: do nothing or throw an error. > This custom variable should also be described in the docstring of > org-speed-command-hook to warn about potential shadowing. > > To summarise, your idea will be reasonable if: > 1. The new behaviour can be customized > 2. The new behaviour is documented in org-speed-command-hook Ok, I agree that this is the most reasonable direction. What do you think about the idea that I outlined in the last post of this thread (https://email@example.com/)?: it consists in defining a new hook (by default with value nil) where the user can store those functions that he wants to have a 'strict' behavior: some functions or all. And then the user should add the org-speed-command-strict-function to org-speed-command-hook. If this idea sounds too hacky, I think a defcustom for org-babel-speed-command-activate, as you suggest, might suffice. Best regards, Juan Manuel
next prev parent reply other threads:[~2022-05-01 11:02 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-30 11:25 Juan Manuel Macías 2022-04-30 13:06 ` Ihor Radchenko 2022-04-30 14:41 ` Juan Manuel Macías 2022-04-30 19:39 ` Juan Manuel Macías 2022-05-01 4:01 ` Ihor Radchenko 2022-05-01 11:00 ` Juan Manuel Macías [this message] 2022-05-02 3:31 ` Ihor Radchenko 2022-05-03 23:08 ` Juan Manuel Macías
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: [PATCH] speed commands: error message when a key is not associated with a command' \ /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).