bug#52876: [External] : Re: bug#52876: 27.2; Call `describe-specified-language-support' without menu-bar

[Drew Adams <drew.adams@oracle.com>]

> > `describe-specified-language-support' raises an error if it is called
> > other than by way of the menu-bar.  Please remove this restriction -
> > make it possible to invoke it any other way as well.
> >
> > See this comment in mule-cmds.el:
> >
> > ;; This function is intended to be called from the menu:
> > ;;   [menu-bar mule describe-language-environment LANGUAGE]
> > ;; and should not run it by `M-x describe-current-input-method-function'.
> 
> We have plenty of commands that are meant to be called from menus
> only

And?  That general observation is irrelevant to a
consideration of any _particular_ command.

> -- they don't make much sense otherwise.

In what way is what `describe-specified-language-support'
does nonsensical if called other than by way of a menu?

That's the question.  Saying that we have commands that
in fact don't make sense if called other than from a
menu is NOT in any way, a reason why that's true of this
command.  Just doesn't follow logically, at all.

> (Ideally they wouldn't be commands visible to the
> environment at all, but that's difficult to achieve.)

No idea what you're on about, there.  But reasoning about
"they" in that way makes no sense.

SOME commands make sense only when called from a menu.
It doesn't follow that every command that we currently
bind only to a menu can't make sense if called another way.

> Closing.

Too bad.