[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: |
Sat, 10 May 2014 10:06:36 +0200 |
User-agent: |
mu4e 0.9.9.6pre3; emacs 24.4.50.1 |
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> (apply #'funcall-interactively (car newcmd) (cdr newcmd))
>
> No, `newcmd' is an expression, so (cdr newcommand) contains arguments
> that need to be evaluated. In some/many cases this evaluation is
> trivial (the args are self-quoting, like nil or integers), but sometimes
> the args can be things like (region-beginning).
Hmm, not sure of this, at least for `repeat-complex-command' something
like (region-beginning) is already evaluated and recorded as an integer
no ?
Oh! ok I see, something like M-: (region-beginning)
will be recorded as something like
(pp-eval-expression (quote (region-beginning)))
>> > (defun funcall-interactively (fun &rest args)
> [sample hack to define funcall-interactively in terms of call-interactively]
>> This won't work IMO, why fun would be a cons or a byte-code-function ?
>
> These are the only interesting cases. The other cases (subrp and
> symbolp, AFAICT) are trivial.
I still don't understand how this would be able to call interactively
something like:
(count-words-region 234 567 nil)
--
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'?, 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
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Stefan Monnier, 2014/05/10
- 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/10
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Michael Heerdegen, 2014/05/11
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Michael Heerdegen, 2014/05/11
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Michael Heerdegen, 2014/05/17
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Stefan Monnier, 2014/05/17
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Stefan Monnier, 2014/05/11
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Thierry Volpiatto, 2014/05/11
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Andreas Röhler, 2014/05/10
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Stefan Monnier, 2014/05/10
- bug#17446: 24.4.50; What is the situation around `called-interactively-p'?, Andreas Röhler, 2014/05/11