From: Eli Zaretskii <eliz@gnu.org>
To: Live System User <nyc4bos@aol.com>
Cc: 33570@debbugs.gnu.org
Subject: bug#33570: 26.1.90; Weirdness with prefix arg and kmacro-end-and-call-macro
Date: Sun, 02 Dec 2018 09:22:56 +0200 [thread overview]
Message-ID: <835zwcbdf3.fsf@gnu.org> (raw)
In-Reply-To: <87bm644q74.fsf@aol.com> (message from Live System User on Sat, 01 Dec 2018 21:28:47 -0500)
> From: Live System User <nyc4bos@aol.com>
> Date: Sat, 01 Dec 2018 21:28:47 -0500
>
> Macro:
>
> 5*; ;; self-insert-command
> C-a ;; move-beginning-of-line
> C-n ;; next-line
>
>
> What I was trying to do was to comment out some lines in
> an elisp file by adding semi-colons, going back to the
> begining of the line and then positoning to the next line.
>
> I tested the macro via "C-x e" (kmacro-end-and-call-macro)
> to make sure it gave the results that I wanted which it did.
> So I then added a prefix argument:
>
> C-u 20 C-x e
> and saw this:
>
> ;;;;;(setq magit-blame-heading-format "%-20a %C %s %H")
> ;;;;;
> ;;;;;(setq magit-branch-read-upstream-first nil)
> ;;;;;(setq magit-branch-arguments nil)
> ;;;;;
> ;;;;;;; FIXME: ADD https://github.com/wuliuxiansheng/Emacs_Configuration/blob/;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;master/lisp/init-vc.el
>
> It looks like the macro did not go to the next line but stayed
> on line 41 of a 51-line buffer.
>
> What happened?
I don't know, since you didn't show the text before the change, and
you only show 6 lines out of 20 that should have been changed.
> Is there an issue with logical/visual lines and its
> interection with "C-a" and/or "C-n" used in keyboard
> macros?
C-n moves by visual lines by default, is that what you asked?
next prev parent reply other threads:[~2018-12-02 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 2:28 bug#33570: 26.1.90; Weirdness with prefix arg and kmacro-end-and-call-macro Live System User
2018-12-02 7:22 ` Eli Zaretskii [this message]
2018-12-02 11:28 ` Live System User
2018-12-02 13:50 ` 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=835zwcbdf3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33570@debbugs.gnu.org \
--cc=nyc4bos@aol.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).