[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17446: 24.4.50; What is the situation around `called-interactively-p
From: |
Thierry Volpiatto |
Subject: |
bug#17446: 24.4.50; What is the situation around `called-interactively-p'? |
Date: |
Fri, 09 May 2014 20:47:04 +0200 |
User-agent: |
mu4e 0.9.9.6pre3; emacs 24.4.50.1 |
Stefan Monnier <monnier@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
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, (continued)
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Drew Adams, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Stefan Monnier, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Drew Adams, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Stefan Monnier, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Drew Adams, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Michael Heerdegen, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Stefan Monnier, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?,
Thierry Volpiatto <=
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Stefan Monnier, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Stefan Monnier, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Stefan Monnier, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Drew Adams, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Stefan Monnier, 2014/05/09
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Thierry Volpiatto, 2014/05/10
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Thierry Volpiatto, 2014/05/10
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Michael Heerdegen, 2014/05/10
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Thierry Volpiatto, 2014/05/10
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Thierry Volpiatto, 2014/05/10