From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: drsl@drshapeless.com, 58210@debbugs.gnu.org
Subject: bug#58210: 29.0.50; Visual line mode movement bug
Date: Sat, 01 Oct 2022 15:49:41 +0300 [thread overview]
Message-ID: <83k05jbtei.fsf@gnu.org> (raw)
In-Reply-To: <871qrrajva.fsf@web.de> (message from Michael Heerdegen on Sat, 01 Oct 2022 13:00:57 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Jacky Li <drsl@drshapeless.com>, 58210@debbugs.gnu.org
> Date: Sat, 01 Oct 2022 13:00:57 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > > Date: Sat, 01 Oct 2022 11:14:35 +0800
> > > From: Jacky Li via "Bug reports for GNU Emacs,
> > > the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> > >
> > >
> > > If visual-line-mode is turned on, using C-a, C-e or C-k will move to the
> > > line above, resulting in a unwanted behaviour. This behaviour was not
> > > observed in the build of Sept 24 HEAD, but in the build of Sept 30
> > > HEAD. I suspect that the bug commit is within this period.
> > >
> > > Also, this bug only happens when visual-line-mode is enabled. The
> > > related interactive functions are (beginning-of-visual-line),
> > > (end-of-visual-line), (kill-visual-line).
> >
> > Sorry about that, should be fixed now.
>
> (vertical-motion 0) now moves to the previous line. I think this is
> not expected...?
Did I fix this now?
next prev parent reply other threads:[~2022-10-01 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 3:14 bug#58210: 29.0.50; Visual line mode movement bug Jacky Li via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-01 6:25 ` Eli Zaretskii
2022-10-01 11:00 ` Michael Heerdegen
2022-10-01 11:21 ` Michael Heerdegen
2022-10-01 12:49 ` Eli Zaretskii [this message]
2022-10-01 13:56 ` drshapeless via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-01 15:02 ` Eli Zaretskii
2022-10-02 4:02 ` drshapeless via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-02 6:10 ` Eli Zaretskii
2022-10-01 14:48 ` Michael Heerdegen
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=83k05jbtei.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58210@debbugs.gnu.org \
--cc=drsl@drshapeless.com \
--cc=michael_heerdegen@web.de \
/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).