Re: Current mode command discovery

[Jean Louis <bugs@gnu.support>]

* Óscar Fuentes <ofv@wanadoo.es> [2021-02-17 02:33]:
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Imagine user confusion and frustration when a command that is known to
> > Help cannot be invoked!
> 
> Why would the user wish to invoke a command that makes no sense on the
> context he is working on? On the best case, the command will just throw
> an error. At worse, it will mess up things.

For consideration let me also mention, that:

- I am developing my commands in such a way that they are related to
  the specific package and to specific derived mode, but that such
  commands shall mostly work outside of the mode as well.

  The mechanism to exclude commands belonging to specific mode shall
  be perfect as not to exclude such commands which may be used both
  globally and mode-specifically.

  Example is my command `cf-tabulates-notes' that could maybe later be
  renamed to `cf-notes' as that one will recognize if it is inside of
  the derived mode and show notes to specific person, but may as well
  be invoked outside of the mode in any other mode, and ask user for
  the person or account to which notes are related to.

- It is not logical to have commands being shown in M-x that cannot be
  anyway invoked in some mode, let us say like:
  `Buffer-menu-backup-unmark' or `Buffer-menu-delete', etc. it is all
  clear that such commands do not belong to every mode.

  Yet I hope that mechanism for discovery of commands that may be
  considered useless in some modes will be good enough as not to
  disable those mode related commands that also work globally,
  including those global commands that are not mode related.

Jean