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

Previous Next

Full log

View this message in rfc822 format

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: bug#17446: 24.4.50; What is the situation around `called-interactively-p'?
Date: Fri, 09 May 2014 20:47:04 +0200

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

>>> > Before we go about doing that, I'd want to know one more thing: how did
>>> > icicles and helm does with it, in previous versions of Emacs?
>>> Icicles did nothing - the bug existed, just as in vanilla Emacs.
>
> In which sense did it exist in vanilla Emacs?

(eval (count-words nil nil))
=> eval: Wrong type argument: integer-or-marker-p, nil

We were using a condition-case returning an error message in such cases.

See

https://lists.gnu.org/archive/html/emacs-bug-tracker/2013-08/msg00161.html

>> It was the same with helm.
>
> IOW, this is a long standing problem, for which
> called-interactively-p-functions provides a limited workaround?

Yes, seems fragile too.

Another approch would be to allow more args to `call-interactively',
this would allow one to use:

(apply 'call-interactively '(sexp arg1 arg2 arg...))

But not sure this would cover all use cases.

-- 
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.