unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Fri, 20 May 2022 10:01:51 +0300	[thread overview]
Message-ID: <83wnegbsbk.fsf@gnu.org> (raw)
In-Reply-To: <87leux8505.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  20 May 2022 01:41:30 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 55514@debbugs.gnu.org
> Date: Fri, 20 May 2022 01:41:30 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Maybe all we need is to add a hook that will be called by
> > kmacro-call-macro before running the macro.  Then users can do
> > whatever they like in that hook, including turning off
> > line-move-visual (which I'm guessing is what you meant, not
> > visual-line-mode).
> 
> But that doesn't really fix the issue -- the non-visual-line-moving
> commands have to be replicated when we execute the macro.

No, you need just turn off line-move-visual in that hook, then C-n
will follow physical lines instead of visual lines, which is AFAIU
what you wanted.





  reply	other threads:[~2022-05-20  7:01 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 [this message]
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
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

  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=83wnegbsbk.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 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).