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

[Drew Adams]

> > How 'bout the patch below,
> BTW, for older Emacsen, you can probably use a hack along the lines of
> the guaranteed 100% untested code below:

Not sure I understand how any of this will help the use cases we
mentioned.  Is the idea that `repeat-complex-command' will, instead
of doing (eval newcmd), do something like this?

 (eval `(funcall-interactively ,(car newcmd) ,@(cdr newcmd)))

For the case in bug #14136, where NEWCMD is (count-words nil nil),
this would mean (funcall-interactively 'count-words nil nil).

(Maybe an `apply-interactively' would be handier here?)

In any case, I will wait to see how this changes the
`repeat-complex-command' code and then do likewise for my code,
which is similar.