Subject: Re: bug#47198: 27.1; Why bind some commands by default if they're not defined?

From: Eli Zaretskii <[email-masked]>
Date: Tue, 16 Mar 2021 20:40:13 +0200

> From: Drew Adams <[email-masked]>
> Date: Tue, 16 Mar 2021 17:57:45 +0000
> 
>  M-s h f		hi-lock-find-patterns
> 
> This is apparently because file `bindings.el' adds the key binding:
> 
>   (define-key search-map "hf"   'hi-lock-find-patterns)
> 
> Is it a good idea that we do this even though the command is not yet
> defined?
> 
> Seems like such a binding should be in hi-lock.el, and be created only
> after the command is created, no?

If the command is in hi-lock.el, how do you cause hi-lock to autoload
when first invoked?