unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Steve Purcell <steve@sanityinc.com>
Cc: 28248@debbugs.gnu.org
Subject: bug#28248: 26.0.50; display-line-numbers does not affect window-width / window-text-width
Date: Tue, 17 Oct 2017 00:56:45 +0300	[thread overview]
Message-ID: <d02bcd3c-a3af-33fb-d131-1d9309c59ac0@yandex.ru> (raw)
In-Reply-To: <834lst5bep.fsf@gnu.org>

Hey Eli,

On 8/27/17 5:32 PM, Eli Zaretskii wrote:
>> and there is also no variable which contains the current width of
>> the line numbers.  This all means there is no way to determine the
>> width of the text area of the window.
> 
> Yes, there is.  From NEWS:
> 
>    Lisp programs that need to know how much screen estate is used up for
>    line-number display in a window can use the new function
>    'line-number-display-width'.

Does it work as documented? E.g., I can enable 
display-line-numbers-mode, and they will take up 4 visual columns 
(numbers plus separators), but (line-number-display-width) returns 2.

Should I always use (+ 2 (line-number-display-width)) instead? That 
would be the actual amount of "screen estate used up for line-number 
display".

Can I rely on the extra value always being 2?





  reply	other threads:[~2017-10-16 21:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-27  5:40 bug#28248: 26.0.50; display-line-numbers does not affect window-width / window-text-width Steve Purcell
2017-08-27  9:15 ` Stephen Berman
2017-08-27 14:37   ` Eli Zaretskii
2017-08-27 14:32 ` Eli Zaretskii
2017-10-16 21:56   ` Dmitry Gutov [this message]
2017-10-17  2:34     ` Eli Zaretskii
2017-10-17  6:19       ` Steve Purcell
2017-10-17  7:01         ` Eli Zaretskii
2017-10-17  7:31           ` Steve Purcell
2017-10-17  8:15             ` Eli Zaretskii
2017-10-17  8:23       ` Dmitry Gutov
2017-10-17 16:33         ` Eli Zaretskii
2017-10-18  0:33           ` Dmitry Gutov
2017-10-18 16:35             ` Eli Zaretskii
2017-10-18 22:40               ` Dmitry Gutov
2017-10-19  3:15                 ` Eli Zaretskii
2017-10-20  9:44                   ` Eli Zaretskii

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=d02bcd3c-a3af-33fb-d131-1d9309c59ac0@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=28248@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=steve@sanityinc.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).