all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 17446@debbugs.gnu.org, Thierry Volpiatto <thierry.volpiatto@gmail.com>
Subject: bug#17446: 24.4.50; What is the situation around `called-interactively-p'?
Date: Sun, 11 May 2014 06:24:19 +0200	[thread overview]
Message-ID: <87siohx7rg.fsf@web.de> (raw)
In-Reply-To: <jwv61ld8ka2.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Sat, 10 May 2014 16:15:42 -0400")

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

> The code I showed takes an interactive function with some args, rips
> the function apart to rebuild a new one whose interactive spec just
> returns those args.  If the function is a symbol, then recurse on
> (symbol-function fun).

Yes, it's a funny idea.

Stefan, what's the right approach to make commands that refer to
this-command or last-command work correctly when called with your code?
Should we add something like

  (when (symbolp fun) (setq this-command fun))  ?

Does your patch planned for later inclusion care about updating
this-command and last-command appropriately?


Thanks,

Michael.





  reply	other threads:[~2014-05-11  4:24 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87siohx7rg.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=17446@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=thierry.volpiatto@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.