Subject: bug#24106: 25.1; Viper triggers warning about interactive-p at startup (cosmetic)

From: Lars Ingebrigtsen <[email-masked]>
Date: Sat, 27 Jul 2019 17:40:50 +0200

Marien Zwart <[email-masked]> writes:

> With the following in ~/.emacs/init.el:
>
>   (package-initialize)
>
>   (setq viper-mode t
>         viper-inhibit-startup-message t
>         viper-expert-level 5
>         )
>
>   (require 'viper)
>
> Emacs pops up a *Compile-Log* buffer at startup, displaying:
>
> Warning (bytecomp): ‘interactive-p’ is an obsolete function (as of
> 23.2); use ‘called-interactively-p’ instead.
>
> Note this use of "require" in my init file is the normal way of loading Viper
> (according to its documentation).
>
> Loading Viper in a running Emacs did not trigger the error message.
> Only having it in my init file did.
>
> Removing the interactive-p call from the self-insert-command defadvice
> in viper.el removes the warning.

Looks like this has been fixed recently for Emacs 27 (viper.el no longer
uses interactive-p), so I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no