From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Rankin <hello@paulwrankin.com>, 29597@debbugs.gnu.org
Subject: bug#29597: 26.0.90; line-number-display-width returns incorrect width
Date: Fri, 8 Dec 2017 10:37:09 -0500 [thread overview]
Message-ID: <CAM-tV-_cnF1wp2CSrHeaS_-miuj8wB_tLUMtQG1-76b1gayK5A@mail.gmail.com> (raw)
In-Reply-To: <838tedw9el.fsf@gnu.org>
On Fri, Dec 8, 2017 at 10:01 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> I understand that this function is also used internally for specific purposes, so it needs to behave a specific way to appease the initial writer of the code. But for the sake of sanity, I strongly suggest either fixing this function or creating a separate “public” function that operates vaguely in line with user expectation for those of us wanting to accommodate display-line-numbers-mode.
>
> Sorry, I don't understand what is missing. If you wanted the value of
> 4 in your case, you need to call this function like this:
>
> (line-number-display-width 'columns)
>
> as documented.
I think the idea would to split that function into 2 simpler ones, e.g.:
(line-number-display-columns) => 4
(line-number-display-width) => 2
(line-number-display-width t) => the equivalent in pixels
next prev parent reply other threads:[~2017-12-08 15:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 5:34 bug#29597: 26.0.90; line-number-display-width returns incorrect width Paul Rankin
2017-12-07 8:55 ` Eli Zaretskii
2017-12-08 1:44 ` Paul Rankin
2017-12-08 2:00 ` Noam Postavsky
2017-12-08 2:32 ` Paul Rankin
2017-12-08 15:01 ` Eli Zaretskii
2017-12-08 15:37 ` Noam Postavsky [this message]
2017-12-08 15:53 ` Eli Zaretskii
2017-12-08 15:55 ` Eli Zaretskii
2017-12-08 16:23 ` Noam Postavsky
2017-12-08 16:29 ` Eli Zaretskii
2017-12-08 22:39 ` Noam Postavsky
2017-12-08 14:22 ` Eli Zaretskii
2017-12-08 14:40 ` Noam Postavsky
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=CAM-tV-_cnF1wp2CSrHeaS_-miuj8wB_tLUMtQG1-76b1gayK5A@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=29597@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=hello@paulwrankin.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 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.