From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29664@debbugs.gnu.org, kaushal.modi@gmail.com
Subject: bug#29664: 26.0.90; Auto Hscroll Mode + Visual Line Mode + Truncate don't work well together
Date: Sat, 04 Sep 2021 08:41:05 +0200 [thread overview]
Message-ID: <87r1e4u9ku.fsf@gnus.org> (raw)
In-Reply-To: <83wnnyx7e3.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 03 Sep 2021 13:47:48 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> > It is a problem, but I don't know what to do about that except saying
>> > "don't do that".
>>
>> So maybe some change in the docs is in order?
Mentioning this in the `truncate-lines' doc would be fine...
> Alternatively, we could use add-variable-watcher to disable
> visual-line-mode when one of these variables is set, similarly with
> what we do to force redisplay of a buffer when some variables are
> modified (see the end of frame.el).
... but this seems like overkill to me. I don't think anybody would
actually imagine that these two things could be mixed -- the original
bug report was just about somebody who had both thing set accidentally,
and then wondering what's going on. (And the change to
toggle-truncate-lines I pushed should make that accident less likely to
occur.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-09-04 6:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 20:22 bug#29664: 26.0.90; Auto Hscroll Mode + Visual Line Mode + Truncate don't work well together Kaushal Modi
2017-12-11 20:56 ` Eli Zaretskii
2017-12-11 21:07 ` Kaushal Modi
2017-12-12 3:30 ` Eli Zaretskii
2017-12-12 8:02 ` Noam Postavsky
2021-09-03 6:36 ` Lars Ingebrigtsen
2021-09-03 7:06 ` Eli Zaretskii
2021-09-03 7:12 ` Lars Ingebrigtsen
2021-09-03 7:23 ` Eli Zaretskii
2021-09-03 10:47 ` Eli Zaretskii
2021-09-04 6:41 ` Lars Ingebrigtsen [this message]
2021-09-04 10:38 ` Eli Zaretskii
2021-09-03 7:57 ` Juri Linkov
2021-09-03 8:16 ` Lars Ingebrigtsen
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=87r1e4u9ku.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=29664@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kaushal.modi@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).