unknown property special warnings was fix interactive spec for kill-region

[T.V. Raman]

P.S. Does anyone know what  causes this warning:

Warning: Unknown defun property special in emacspeak-should-i-fix-interactive-p
-- 

-- 


On 9/7/12, T.V. Raman <address@hidden> wrote:
> Here is the byte-compiler warning:
>
> emacs -batch -q -no-site-file   -eval '(setq vc-handled-backends nil
> byte-compile-warnings t)'  -l ".."/lisp/emacspeak-load-path.el -l
> ".."/lisp/emacspeak-loaddefs.el -l ".."/lisp/emacspeak-cus-load.el -l
> ".."/lisp/g-client/g-load-path.el  -f batch-byte-compile
> emacspeak-advice.el
> Warning: Unknown defun property special in
> emacspeak-should-i-fix-interactive-p
>
> In toplevel form:
> emacspeak-advice.el:1607:52:Warning: ad-Orig-kill-region called with 3
>     arguments, but accepts only 2
>
> Line 1607 is the last line of this advice form:
>
> (defadvice kill-region (around emacspeak pre act)
>   "Indicate region has been killed.
> Use an auditory icon if possible."
>   (cond
>    ((ems-interactive-p )
>     (let ((count (count-lines (region-beginning) (region-end))))
>       ad-do-it
>       (emacspeak-auditory-icon 'delete-object )
>       (message "Killed region containing %s lines" count)))
>    (t ad-do-it))
>   ad-return-value)
>
>  I'll attach just the advice form that triggers the error:
> --
>
> --
>
>
> On 9/3/12, Stefan Monnier <address@hidden> wrote:
>>> The signature doesn't match, and you get byte compiler warnings.
>>
>> Please report the actual byte-compilation warnings instead, then.
>> I have a strong feeling you're confused about the source of the problem
>> (which probably comes from the fact that the 3 optional argument was
>> made obsolete and is hidden by an advertised signature).
>>
>>
>>         Stefan
>>
>