From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org, gregory@heytings.org
Subject: Re: master 616da8fa8e: Merge branch 'feature/fix-the-long-lines-display-bug'
Date: Thu, 21 Jul 2022 15:40:45 +0300 [thread overview]
Message-ID: <83v8rqmyeq.fsf@gnu.org> (raw)
In-Reply-To: <87y1wm7ipn.fsf@yahoo.com> (message from Po Lu on Thu, 21 Jul 2022 20:28:52 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Gregory Heytings <gregory@heytings.org>
> Date: Thu, 21 Jul 2022 20:28:52 +0800
>
> Gregory Heytings <gregory@heytings.org> writes:
>
> > + doc: /* Line length above which specific display optimizations are used.
> > +Display optimizations for long lines will automatically be enabled in
> > +buffers which contain one or more lines whose length is above that
> > +threshold.
> > +When nil, these display optimizations are disabled. */);
>
> What are the "specific display optimizations"?
Read the code ;-)
Or maybe I don't understand what you are asking about.
next prev parent reply other threads:[~2022-07-21 12:40 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 [this message]
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
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
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=83v8rqmyeq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=luangruo@yahoo.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).