From: Andrey Listopadov <andreyorst@gmail.com>
To: Gregory Heytings <gregory@heytings.org>, Eli Zaretskii <eliz@gnu.org>
Cc: "Gerd Möllmann" <gerd.moellmann@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 07:12:08 +0000 [thread overview]
Message-ID: <EA2D3A79-F85D-44EA-A3FA-A0A81F86DD50@gmail.com> (raw)
In-Reply-To: <8a3eaeef01b9a103450a@heytings.org>
> 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,
I imagine there's not that big of a percent of Emacs users who open files
with a really long lines (given the issues with these), and for all of those
there's an even smaller percent of those who use truncate-lines (and
even smaller percent of those who would submit a report, perhaps).
Overall, I'd like not to lose the ability to view long lines in such logs with truncated lines enabled, because as I've said earlier, it allows me to partially compare line to above and below ones, without scrolling. And I rarely even scroll to the right that much in such logs, as there's just way too much information to be viewed in a single horizontal line.
If, however nothing will prevent me from enabling truncating even if optimizations are in place, I'm OK with disabling truncating by default.
next prev parent reply other threads:[~2022-07-26 7:12 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 [this message]
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=EA2D3A79-F85D-44EA-A3FA-A0A81F86DD50@gmail.com \
--to=andreyorst@gmail.com \
--cc=56683@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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.