unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
	andreyorst@gmail.com, 56683@debbugs.gnu.org
Subject: bug#56683: 29.0.50; long lines fix doesn't work correctly when lines are truncated
Date: Mon, 25 Jul 2022 22:22:22 +0000	[thread overview]
Message-ID: <8a3eaeef01b9a103450a@heytings.org> (raw)
In-Reply-To: <83r12djjvm.fsf@gnu.org>


By the way, we should also decide what to do when the user enables 
truncate-lines in a buffer with "really too long" lines.  With 
DISP_INFINITY == 10000000 (its current value), and with a character pixel 
width of 20 (a not uncommon value nowadays with HiDPI screens), lines 
longer than 500000 (single-width) characters will not be displayed 
correctly.  With a larger character pixel width, or with characters 
occupying more than one column, that would be even less.

Given:

1. that there has not been a single bug report about the fact that 
truncate-line does not work correctly with "really too long" lines in the 
last 20 years,

2. that the limit above, caused by DISP_INFINITY, is not much more than 
10000, the default value for long-line-threshold, and

3. the remaining slowdowns caused by truncate-lines,

I'd be in favor of simply disabling truncate-lines when 
long_line_optimizations_p is set.





  reply	other threads:[~2022-07-25 22:22 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
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 [this message]
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

  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=8a3eaeef01b9a103450a@heytings.org \
    --to=gregory@heytings.org \
    --cc=56683@debbugs.gnu.org \
    --cc=andreyorst@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@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 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).