From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 17446@debbugs.gnu.org
Subject: bug#17446: 24.4.50; What is the situation around `called-interactively-p'?
Date: Fri, 09 May 2014 20:47:04 +0200 [thread overview]
Message-ID: <87r442x00n.fsf@gmail.com> (raw)
In-Reply-To: <jwveh02dema.fsf-monnier+emacsbugs@gnu.org>
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
next prev parent reply other threads:[~2014-05-09 18:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 12:29 bug#17446: 24.4.50; What is the situation around `called-interactively-p'? Thierry Volpiatto
2014-05-09 13:39 ` Drew Adams
2014-05-09 14:11 ` Michael Heerdegen
2014-05-09 14:47 ` Drew Adams
2014-05-09 14:17 ` Drew Adams
2014-05-09 14:15 ` Stefan Monnier
2014-05-09 14:28 ` Drew Adams
2014-05-09 14:50 ` Stefan Monnier
2014-05-09 14:55 ` Drew Adams
2014-05-09 15:15 ` Michael Heerdegen
2014-05-09 17:53 ` Stefan Monnier
2014-05-09 18:47 ` Thierry Volpiatto [this message]
2014-05-09 19:50 ` Stefan Monnier
2014-05-09 21:02 ` Stefan Monnier
2014-05-09 22:39 ` Stefan Monnier
2014-05-09 23:34 ` Drew Adams
2014-05-10 2:13 ` Stefan Monnier
2014-05-10 9:10 ` Thierry Volpiatto
2014-05-10 6:12 ` Thierry Volpiatto
2014-05-10 7:40 ` Michael Heerdegen
2014-05-10 8:41 ` Thierry Volpiatto
2014-05-10 5:51 ` Thierry Volpiatto
2014-05-10 6:45 ` Stefan Monnier
2014-05-10 8:06 ` Thierry Volpiatto
2014-05-10 20:15 ` Stefan Monnier
2014-05-11 4:24 ` Michael Heerdegen
2014-05-11 5:58 ` Michael Heerdegen
2014-05-17 18:01 ` Michael Heerdegen
2014-05-18 1:56 ` Stefan Monnier
2014-05-11 6:02 ` Stefan Monnier
2014-05-11 4:31 ` Thierry Volpiatto
2014-05-10 10:22 ` Andreas Röhler
2014-05-10 20:19 ` Stefan Monnier
2014-05-11 7:47 ` Andreas Röhler
2014-05-10 3:43 ` Thierry Volpiatto
2017-03-25 6:23 ` npostavs
2014-05-09 19:16 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r442x00n.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=17446@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).