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: Thu, 19 May 2022 10:08:18 +0300 [thread overview]
Message-ID: <837d6idmot.fsf@gnu.org> (raw)
In-Reply-To: <87o7zu9tay.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 19 May 2022 03:59:01 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 19 May 2022 03:59:01 +0200
>
> visual-line-mode is nice, but it has one major drawback -- it makes
> <down> not "reliable" when recording macros.
>
> That is, if you record
>
> C-x ( C-SPC <down> <down> C-k C-x )
>
> (i.e., "kill two lines"), you can't really use `C-x e' to do much of
> anything, because the buffer may have too-long lines that makes <down>
> move down into the middle of a logical line.
>
> So perhaps we should have a user option that remaps
> next-line/previous-line to next-logical-line/previous-logical-line while
> inside a `C-x ('?
>
> (Or something to that effect -- perhaps the user option should make `C-x
> (' switch visual-line-mode off and exiting recording switches it on
> again (and the recorded macro would also contain those commands).
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).
We could also have a new user option to turn that off automatically
while running a macro, but that sounds too specific to some uses of
macros in some use cases, not something many users will want in many
cases.
next prev parent reply other threads:[~2022-05-19 7:08 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 [this message]
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
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=837d6idmot.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.