bug#17446: 24.4.50; What is the situation around `called-interactively-p'?

[Stefan Monnier]

> Another approch would be to allow more args to `call-interactively',
> this would allow one to use:

> (apply 'call-interactively '(sexp arg1 arg2 arg...))

> But not sure this would cover all use cases.

Right, I'm thinking of introducing a new `funcall-interactively' which
is just like `funcall' except that the called function will see its
`called-interactively-p' returning non-nil.

But I think this will have to wait for 24.5.


        Stefan