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

[Stefan Monnier]

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

Unrelated.  It's obsolete because it's replaced by called-interactively-p.
The discussion here applies just as much about interactive-p as about
called-interactively-p.

And using/introducing funcall-interactively doesn't solve all the other
problems with interactive-p/called-interactively-p, such as the fact
that they may (depending on the position of the sun) return nil rather
than t if called within an `unwind-protect'.


        Stefan