From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: 23570@debbugs.gnu.org
Subject: bug#23570: 25.1.50; Cursor motion error with visual-line-mode
Date: Sat, 21 May 2016 12:39:09 +0300 [thread overview]
Message-ID: <83posf7nsy.fsf@gnu.org> (raw)
In-Reply-To: <87oa81jxyu.fsf@gmail.com> (message from Chong Yidong on Fri, 20 May 2016 09:54:17 +0800)
> From: Chong Yidong <cyd@gnu.org>
> Cc: 23570@debbugs.gnu.org
> Date: Fri, 20 May 2016 09:54:17 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > the first word that wraps to the next screen line is followed by more
> > than one whitespace character. In your recipe, that would be the 2
> > spaces in "ABCDEFGHIJK MOPQ".
>
> Yes, the two whitespaces on the wrapped line seem to be necessary to
> trigger the bug.
>
> > I wonder what your real-life use cases where
>
> I came across this while editing a LaTeX document, and the two white
> spaces that triggered the bug were the usual two spaces after a full
> stop. I'd previously noticed the bug on a couple of occasions, sometime
> after the Emacs 24.4 release, but didn't manage to get a reproducible
> recipe until now.
Thanks, I've pushed a fix to the master branch (commit 99848b3).
Please test.
(I think this change is too low-level to be safe for the emacs-25
branch at this late stage of pretest.)
next prev parent reply other threads:[~2016-05-21 9:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 11:20 bug#23570: 25.1.50; Cursor motion error with visual-line-mode Chong Yidong
2016-05-18 18:27 ` Eli Zaretskii
2016-05-19 2:58 ` Chong Yidong
2016-05-19 4:38 ` Eli Zaretskii
2016-05-19 12:56 ` martin rudalics
2016-05-19 16:50 ` Eli Zaretskii
2016-05-19 17:18 ` Eli Zaretskii
2016-05-20 1:54 ` Chong Yidong
2016-05-21 9:39 ` Eli Zaretskii [this message]
2016-05-23 2:09 ` Chong Yidong
2016-05-23 2:36 ` Eli Zaretskii
2016-05-23 6:49 ` John Wiegley
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=83posf7nsy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23570@debbugs.gnu.org \
--cc=cyd@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.