unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55514@debbugs.gnu.org
Subject: bug#55514: 29.0.50; Keyboard macros and visual-line-mode
Date: Sun, 22 May 2022 13:14:37 +0200	[thread overview]
Message-ID: <87r14lx1ia.fsf@gnus.org> (raw)
In-Reply-To: <83h75j7zqa.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 21 May 2022 16:59:57 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> 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?

That is what this bug report is about -- recording and executing macros.

> 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.

I think we'll just have to let this rest for a while, because we've been
over this too many times.  The original bug report really has all the
details.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-05-22 11:14 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
2022-05-22 11:14                       ` Lars Ingebrigtsen [this message]
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=87r14lx1ia.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=55514@debbugs.gnu.org \
    --cc=eliz@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.
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).