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

Previous Next

Full log

Message #65 received at 17446 <at> debbugs.gnu.org (full text, mbox):

From: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: Michael Heerdegen <michael_heerdegen <at> web.de>, 17446 <at> debbugs.gnu.org,
 Drew Adams <drew.adams <at> oracle.com>
Subject: Re: bug#17446: 24.4.50;
 What is the situation around `called-interactively-p'?
Date: Sat, 10 May 2014 08:12:28 +0200

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

>> 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:
>
>    (defun funcall-interactively (fun &rest args)
>      (call-interactively
>        (cond
>         ((consp fun)
>          (mapcar (lambda (x)
>                    (if (eq (car-safe x) 'interactive))
                                                       ^
>                      `(interactive ',args) x)
>                  fun))
>         ((byte-code-function-p)
                                ^ missing arg ?
>          (apply #'make-byte-code
>                 (aref 0 fun)
>                 (aref 1 fun)
>                 (aref 2 fun)
>                 (aref 3 fun)
>                 (aref 4 fun)
>                 `',args)))))

This won't work IMO, why fun would be a cons or a byte-code-function ?
 
-- 
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.