From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: 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: Tue, 26 Jul 2022 15:37:41 +0300 [thread overview]
Message-ID: <83r128cane.fsf@gnu.org> (raw)
In-Reply-To: <ad567fa90a52badace47@heytings.org> (message from Gregory Heytings on Tue, 26 Jul 2022 12:17:33 +0000)
> Date: Tue, 26 Jul 2022 12:17:33 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: gerd.moellmann@gmail.com, andreyorst@gmail.com, 56683@debbugs.gnu.org
>
> > Maybe optionally. Or maybe displaying a message/warning suggesting
> > that. I don't like disabling truncate-lines unconditionally in such
> > buffers, I prefer leaving that to the user.
>
> The user would still have the choice to disable the automatic disabling by
> setting long-line-threshold to nil.
Yes, I understand. I still don't like it very much. But if many
users will complain, we might change that before Emacs 29 is released.
> > And I think we should use INT_MAX instead of DISP_INFINITY, for the
> > purpose of auto-hscroll. (There are several other uses of that macro,
> > but I didn't yet look at all of them to see if it would make sense to
> > increase DISP_INFINITY itself.)
>
> But you said earlier that this was undesirable because it would affect
> performance?
No, I said making the type of the struct member current_x a ptrdiff_t
or intmax_t will affect performance. The above doesn't propose any
such changes, it just enlarges the "infinity" value. With that value,
lines up to (/ (expt 2 31) 20) => 107374182 (i.e. about 107 million
characters) per line will still display correctly with truncate-lines
when hscrolling is required.
next prev parent reply other threads:[~2022-07-26 12:37 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
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 [this message]
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=83r128cane.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56683@debbugs.gnu.org \
--cc=andreyorst@gmail.com \
--cc=gerd.moellmann@gmail.com \
--cc=gregory@heytings.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.