From: Gregory Heytings <gregory@heytings.org>
To: Andrey Listopadov <andreyorst@gmail.com>
Cc: 56683@debbugs.gnu.org
Subject: bug#56683: 29.0.50; long lines fix doesn't work correctly when lines are truncated
Date: Thu, 21 Jul 2022 19:45:19 +0000 [thread overview]
Message-ID: <b7551196d54434aeb8a7@heytings.org> (raw)
In-Reply-To: <87h73ab8bo.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
>
> I'm using emacs with `truncate-lines` set to `t` in my init.el. After
> the merge of #56393 I've rebuilt Emacs, and started testing the fix.
> I've noticed, that when lines are truncated, opening dictionary.json
> from the #45898 and pressing C-e doesn't move you to the end of the
> line, but stops somewhere inside it. E.g. with the default window width
> of Emacs -Q, I can see the following portion of the line
>
> ←, "hu": ["index"]}, "examples": [["en C la indicoj aperas interortajkrampoj, →
>
> Arrows shown in the fringe indicate that there are more to the line on
> the right side.
>
You would have seen the same bug before the merge, so it's entirely
unrelated to the merge. It is present at least in Emacs 24, 25, 26, 27
and 28.
>
> As a side question, does these optimizations work with truncated lines?
> As far as I can tell Emacs is not as responsive as when the lines are
> wrapped, but I don't know how to measure this precisely.
>
They do work with truncated lines, but I suspect that truncated lines
require specific fixes to work efficiently.
next prev parent reply other threads:[~2022-07-21 19:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 18:49 bug#56683: 29.0.50; long lines fix doesn't work correctly when lines are truncated Andrey Listopadov
2022-07-21 19:45 ` Gregory Heytings [this message]
2022-07-21 19:57 ` Eli Zaretskii
2022-07-21 20:15 ` Gregory Heytings
2022-07-22 6:13 ` Eli Zaretskii
2022-07-22 6:51 ` Gerd Möllmann
2022-07-22 7:28 ` Eli Zaretskii
2022-07-22 7:52 ` Gerd Möllmann
2022-07-22 11:54 ` Eli Zaretskii
2022-07-22 12:56 ` Gerd Möllmann
2022-07-22 13:36 ` Eli Zaretskii
2022-07-22 13:54 ` Gerd Möllmann
2022-07-22 14:35 ` Eli Zaretskii
2022-07-25 22:22 ` Gregory Heytings
2022-07-26 7:12 ` Andrey Listopadov
2022-07-26 7:32 ` Gregory Heytings
2022-07-26 12:15 ` Eli Zaretskii
2022-07-26 11:42 ` Eli Zaretskii
2022-07-26 12:17 ` Gregory Heytings
2022-07-26 12:37 ` Eli Zaretskii
2022-07-26 12:50 ` Gregory Heytings
2022-07-26 13:15 ` Eli Zaretskii
2022-07-26 13:25 ` Gregory Heytings
2022-07-26 17:26 ` Eli Zaretskii
2022-07-26 20:14 ` Gregory Heytings
2022-07-22 6:53 ` Gerd Möllmann
2022-07-22 7:31 ` Eli Zaretskii
2022-07-22 7:53 ` Gerd Möllmann
2022-07-22 11:01 ` Eli Zaretskii
2022-07-21 20:31 ` Andrey Listopadov
2022-07-21 20:52 ` Gregory Heytings
2022-07-22 5:03 ` Andrey Listopadov
2022-07-22 6:34 ` Gregory Heytings
2022-07-22 6:30 ` Eli Zaretskii
2022-07-22 7:28 ` Gerd Möllmann
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=b7551196d54434aeb8a7@heytings.org \
--to=gregory@heytings.org \
--cc=56683@debbugs.gnu.org \
--cc=andreyorst@gmail.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 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.