From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55514@debbugs.gnu.org
Subject: bug#55514: 29.0.50; Keyboard macros and visual-line-mode
Date: Sat, 21 May 2022 16:59:57 +0300 [thread overview]
Message-ID: <83h75j7zqa.fsf@gnu.org> (raw)
In-Reply-To: <878rqvxaxu.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 21 May 2022 15:38:37 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 55514@debbugs.gnu.org
> Date: Sat, 21 May 2022 15:38:37 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > And what do you mean by "execute the same as they were recorded"?
>
> Moving logically versus visually.
Not sure I follow. When you recorded the macro, was C-n moving by
logical lines or by screen lines? If the former, how did you get it
to move by logical lines, when the default is to move by screen lines?
> >> I think having <down> recorded as `M-x next-logical-line' (etc), or
> >> something to that effect, is the way to go here.
> >
> > That's trivial to program, so I'm not sure I understand why would we
> > need that in core.
>
> Trivial how?
Write a command that binds line-move-visual to nil and invokes
next-line, then bind it to some key, and use that key when you record
the macro.
But maybe your answer to my first questions above will explain to me
that I misunderstood you all the way.
next prev parent reply other threads:[~2022-05-21 13:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 1:59 bug#55514: 29.0.50; Keyboard macros and visual-line-mode Lars Ingebrigtsen
2022-05-19 7:08 ` Eli Zaretskii
2022-05-19 23:41 ` Lars Ingebrigtsen
2022-05-20 7:01 ` Eli Zaretskii
2022-05-20 7:14 ` Lars Ingebrigtsen
2022-05-20 7:22 ` Eli Zaretskii
2022-05-20 7:26 ` Lars Ingebrigtsen
2022-05-20 10:46 ` Eli Zaretskii
2022-05-21 11:40 ` Lars Ingebrigtsen
2022-05-21 12:41 ` Eli Zaretskii
2022-05-21 13:38 ` Lars Ingebrigtsen
2022-05-21 13:59 ` Eli Zaretskii [this message]
2022-05-22 11:14 ` Lars Ingebrigtsen
2022-05-22 13:00 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h75j7zqa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55514@debbugs.gnu.org \
--cc=larsi@gnus.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.
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.