unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Len Trigg <lenbok@gmail.com>
Cc: 48095-done@debbugs.gnu.org
Subject: bug#48095: 28.0.50; display-line-numbers-mode / display-line-numbers-width-start incorrect
Date: Fri, 30 Apr 2021 10:36:45 +0300	[thread overview]
Message-ID: <83czuccjg2.fsf@gnu.org> (raw)
In-Reply-To: <CAOGVwemGqucMJMCCdDEUDw_FaSGgEaNMPu8aiXLky2DDPh-T=g@mail.gmail.com> (message from Len Trigg on Fri, 30 Apr 2021 10:29:23 +1200)

> From: Len Trigg <lenbok@gmail.com>
> Date: Fri, 30 Apr 2021 10:29:23 +1200
> Cc: 48095@debbugs.gnu.org
> 
> That seems to work perfectly for my goal (and I assume the intent of display-line-numbers-width-start) of
> having the width stay fixed unless content gets added to the buffer. It might help to add guidance in the docs
> that extra lines would typically be set to the maximum window height.

Thanks, I added that to the doc string.

> Or maybe that value could instead be
> automatically computed from the height of the tallest emacs frame at that time? I assume that's not too
> intensive to determine since it happens once when the mode is activated?

This would be over-engineering, IMO.  First, some people tend to have
lots of frames, so this might be expensive.  Second, what matters is
not the frame height but the window height, and we could have many
windows even if the number of frames is small.  Third, some frames and
windows could be dedicated to special displays, and thus not really
relevant (example: Speedbar frames), so we will no doubt be asked to
provide yet another defcustom, to let users control which frames are
exempt from accounting for their height.

So I think asking users to provide a value strikes a good balance
between functionality and complexity, at least unless we hear about
use cases where automatic adjustment would really make a lot of sense.

With that in mind, I installed the change on the master branch, and
I'm closing this bug report.





  reply	other threads:[~2021-04-30  7:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  2:43 bug#48095: 28.0.50; display-line-numbers-mode / display-line-numbers-width-start incorrect Len Trigg
2021-04-29  9:03 ` Eli Zaretskii
2021-04-29 22:29   ` Len Trigg
2021-04-30  7:36     ` Eli Zaretskii [this message]
2021-04-30 10:56       ` Len Trigg

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=83czuccjg2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=48095-done@debbugs.gnu.org \
    --cc=lenbok@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).