From: Tino Calancha <tino.calancha@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 25860@debbugs.gnu.org,
Marek Twardochlib <wasserwerk.studio@googlemail.com>,
tino.calancha@gmail.com
Subject: bug#25860: 25.1; Double macro execution
Date: Sat, 25 Feb 2017 14:41:36 +0900 [thread overview]
Message-ID: <8760jyx1wv.fsf@calancha-pc> (raw)
In-Reply-To: <87zihbbrxr.fsf@linux-m68k.org> (Andreas Schwab's message of "Fri, 24 Feb 2017 15:10:24 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Feb 24 2017, Marek Twardochlib <wasserwerk.studio@googlemail.com> wrote:
>
>> Then I define another macro that simply call the previous macro
>> insert-a.
>
> How did you do that?
DUNNO how to solve the problem, but i guess th OP means the following:
(defun insert-a-fn (&optional arg)
(interactive "p")
(insert "a\n"))
F3 a RET F4
C-x C-k n insert-a RET
(symbol-function 'insert-a)
=>
(lambda (&optional arg)
"Keyboard macro."
(interactive "p")
(kmacro-exec-ring-item (quote ([97 return] 0 "%d")) arg))
I) ;;; Using `insert-a-fn' we insert "a" _once_:
F3 M-x insert-a-fn RET F4
;; Keyboard Macro Editor. Press C-c C-c to finish; press C-x k RET to cancel.
;; Original keys: <<insert-a-fn>>
Command: last-kbd-macro
Key: none
Macro:
<<insert-a-fn>> ;; insert-a-fn
II) ;;; Using macro `insert-a' we insert "a" _twice_; so you need to remove
;;; <<insert-a>> line by hand:
F3 M-x insert-a RET F4
C-x C-k e RET
;; Keyboard Macro Editor. Press C-c C-c to finish; press C-x k RET to cancel.
;; Original keys: <<insert-a>> a RET
Command: last-kbd-macro
Key: none
Macro:
<<insert-a>> ;; insert-a
a ;; self-insert-command
RET ;; newline
next prev parent reply other threads:[~2017-02-25 5:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 9:23 bug#25860: 25.1; Double macro execution Marek Twardochlib
2017-02-24 14:10 ` Andreas Schwab
2017-02-25 5:41 ` Tino Calancha [this message]
2017-02-25 10:10 ` Tino Calancha
2017-02-25 13:27 ` npostavs
2017-02-25 14:48 ` Tino Calancha
2017-02-25 15:26 ` Marek Twardochlib
2017-02-26 5:04 ` Tino Calancha
2017-02-26 7:12 ` npostavs
2017-02-26 15:33 ` Eli Zaretskii
2017-02-26 16:02 ` npostavs
2017-02-27 15:57 ` Eli Zaretskii
2017-02-27 17:18 ` Noam Postavsky
2017-03-03 14:21 ` Eli Zaretskii
2017-09-29 10:29 ` Marek Twardochlib
2017-09-29 11:41 ` Tino Calancha
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=8760jyx1wv.fsf@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=25860@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=wasserwerk.studio@googlemail.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 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).