From: Po Lu <luangruo@yahoo.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: master 616da8fa8e: Merge branch 'feature/fix-the-long-lines-display-bug'
Date: Thu, 21 Jul 2022 21:56:43 +0800 [thread overview]
Message-ID: <87mtd2602s.fsf@yahoo.com> (raw)
In-Reply-To: <b7551196d5320478dbb1@heytings.org> (Gregory Heytings's message of "Thu, 21 Jul 2022 13:50:41 +0000")
Gregory Heytings <gregory@heytings.org> writes:
> Not a boolean, because even if there is no reason for users to change
> the number, there are at least three useful values: always disabled,
> enabled iff the buffer contains long lines, always enabled. Which you
> can get now by setting the variable to nil, 10000, and 0.
Then why isn't that written in the doc string? And with more obvious
values: nil, t, always.
> I'm also pretty sure we would have bug reports if what a "long line"
> is was hardcoded. So from my point of view the variable is fine as it
> is.
Right, so users will complain about a constant in a supposedly
transparent feature? Then it's not as transparent as you think it is.
next prev parent reply other threads:[~2022-07-21 13:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165839997103.16342.15946302166780212268@vcs2.savannah.gnu.org>
[not found] ` <20220721103932.9604DC0F20B@vcs2.savannah.gnu.org>
2022-07-21 12:28 ` master 616da8fa8e: Merge branch 'feature/fix-the-long-lines-display-bug' Po Lu
2022-07-21 12:40 ` Eli Zaretskii
2022-07-21 13:13 ` Po Lu
2022-07-21 13:19 ` Gregory Heytings
2022-07-21 13:26 ` Po Lu
2022-07-21 13:36 ` Gregory Heytings
2022-07-21 13:53 ` Po Lu
2022-07-21 13:56 ` Gregory Heytings
2022-07-21 14:02 ` Po Lu
2022-07-21 14:07 ` Gregory Heytings
2022-07-21 16:24 ` Eli Zaretskii
2022-07-21 13:38 ` Eli Zaretskii
2022-07-21 13:50 ` Gregory Heytings
2022-07-21 13:56 ` Po Lu [this message]
2022-07-21 14:04 ` Gregory Heytings
2022-07-21 15:50 ` Eli Zaretskii
2022-07-21 13:19 ` Eli Zaretskii
2022-07-21 12:41 ` Gregory Heytings
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=87mtd2602s.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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.