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

From: Andreas Röhler <[email-masked]>
Date: Sat, 10 May 2014 12:22:17 +0200

On 10.05.2014 08:45, Stefan Monnier wrote:
>> (apply #'funcall-interactively (car newcmd) (cdr newcmd))
>
> No, `newcmd' is an expression, so (cdr newcommand) contains arguments
> that need to be evaluated.  In some/many cases this evaluation is
> trivial (the args are self-quoting, like nil or integers), but sometimes
> the args can be things like (region-beginning).
>
>>>     (defun funcall-interactively (fun &rest args)
> [sample hack to define funcall-interactively in terms of call-interactively]
>> This won't work IMO, why fun would be a cons or a byte-code-function ?
>
> These are the only interesting cases.  The other cases (subrp and
> symbolp, AFAICT) are trivial.
>
>
>          Stefan
>
>
>
>

So maybe the good old and simple (interactive-p) needs no longer being obsolete?

Andreas