bug#14084: 24.3.50; `substitute-command-keys': allow for expansion of <remap>...

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

> > Specific request, from the bug report - just please
> > modify `substitute-command' to add another arg that
> > provides for the behavior cited:
> >
> > ___
> > Please add an optional arg to `substitute-command-keys' that
> > changes the behavior.  Please allow for these 3 possibilities:
> 
> I asked for an explanation of what the circumstances you wanted to see
> the different expansions were.  Restating the original bug report
> doesn't help here, but that's par for the course with your responses,
> of course, so that's OK.

It doesn't matter for what circumstances someone
would want to use the new arg to specify any of
the 3 possible behaviors it should provide.

It's up to _callers_ to choose which of those
behaviors to specify.  The new arg should allow
a caller to get any of the 3 behaviors - that's
the request.

The enhancement specifies what's requested.  How
or where Emacs itself might choose to use one
of the behaviors is irrelevant to the request,
and thus beyond its scope.  If you want to change
any callers in Emacs's own code, that's up to you.

My concern is for use of the function by users.
That's why I made the request.

Your apparent confusion about the idea of users
using Elisp functions is perhaps par for the
course.  But yes, Elisp, and Emacs generally, is
for _users_.