all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jacky Li <drsl@drshapeless.com>, 58210@debbugs.gnu.org
Subject: bug#58210: 29.0.50; Visual line mode movement bug
Date: Sat, 01 Oct 2022 13:00:57 +0200	[thread overview]
Message-ID: <871qrrajva.fsf@web.de> (raw)
In-Reply-To: <834jwocb78.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Oct 2022 09:25:15 +0300")

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

Michael.





  reply	other threads:[~2022-10-01 11:00 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 [this message]
2022-10-01 11:21     ` Michael Heerdegen
2022-10-01 12:49     ` Eli Zaretskii
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871qrrajva.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=58210@debbugs.gnu.org \
    --cc=drsl@drshapeless.com \
    --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 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.