unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: drshapeless <drsl@drshapeless.com>
Cc: 58210-done@debbugs.gnu.org
Subject: bug#58210: 29.0.50; Visual line mode movement bug
Date: Sun, 02 Oct 2022 09:10:19 +0300	[thread overview]
Message-ID: <83mtaeah84.fsf@gnu.org> (raw)
In-Reply-To: <878rlyan5x.fsf@drshapeless.com> (message from drshapeless on Sun, 02 Oct 2022 12:02:02 +0800)

> From: drshapeless <drsl@drshapeless.com>
> CC: 58210@debbugs.gnu.org
> Date: Sun, 02 Oct 2022 12:02:02 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: drshapeless <drsl@drshapeless.com>
> >> CC: 58210@debbugs.gnu.org
> >> Date: Sat, 01 Oct 2022 21:56:33 +0800
> >> 
> >> > Did I fix this now?
> >> 
> >> No, it becomes even weirder. C-k seems to be fixed.
> >> 
> >> For C-a, if the point is at an empty line, it works fine. But if the
> >> point is at a line with any chars, it will move to the line above.
> >> 
> >> For C-e, it is fine on an empty line. It is also fine if the point is at
> >> any position of a line with chars, except for at the end of a line, it
> >> will still move to the line above.
> >
> > And now?
> 
> Yes, it is fixed now.

Thanks, closing.





  reply	other threads:[~2022-10-02  6:10 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
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 [this message]
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=83mtaeah84.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58210-done@debbugs.gnu.org \
    --cc=drsl@drshapeless.com \
    /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).