Re: More expclit guidelines for key-binding conventions

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > In the cases where this is out of ignorance, I was thinking that adding
  > a package-lint rule might help.   Not everyone runs package-lint (or its
  > flymake backend), so ideally a byte-compiler or checkdoc warning would
  > be better,

I think it would be good to set up a warning like this.  But not with
a byte-compiler warning, since the warning should not be limited to
compilation.  As for checkdoc, that seems to check for style in
documentation strings.

What occurs to me is to make `define-key' give the warning.

               but I'm not sure how these can be made to apply only to
  > features as opposed to the user-init-file.

We could create a global variable which is normally nil,
but bound to t while loading the user's init files.
Perhaps call it `loading-init-files'.

If that variable is non-nil, that would inhibit this warning.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)