From: joshebosh@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Re: Why this macro error: "After 0 kbd macro iterations: Keyboard macro terminated by a command ringing the bell"
Date: Wed, 20 Jun 2018 13:52:52 -0700 (PDT) [thread overview]
Message-ID: <2dd2fc97-2a9b-43b7-83a3-5f1070f797b3@googlegroups.com> (raw)
In-Reply-To: <20011013142446.A6903@spawar.navy.mil>
for what it's worth for other stumbling upon this
"After 0 kbd macro iterations: Keyboard macro terminated by a command ringing the bell"
I had the same file opened in background in another gnu screen window.
Simply closed the one that gave the error, located the gnu screen window where is was opened (using "jobs" and "fg" on bash), and it works fine.
So a duplicate unsaved copy of file running in background in emacs can cause this error to appear.
Cheers
next parent reply other threads:[~2018-06-20 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011013142446.A6903@spawar.navy.mil>
2018-06-20 20:52 ` joshebosh [this message]
2018-06-21 2:38 ` Why this macro error: "After 0 kbd macro iterations: Keyboard macro terminated by a command ringing the bell" Eli Zaretskii
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=2dd2fc97-2a9b-43b7-83a3-5f1070f797b3@googlegroups.com \
--to=joshebosh@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).