From: Eli Zaretskii <eliz@gnu.org>
To: Steve Purcell <steve@sanityinc.com>
Cc: 28248@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#28248: 26.0.50; display-line-numbers does not affect window-width / window-text-width
Date: Tue, 17 Oct 2017 11:15:12 +0300 [thread overview]
Message-ID: <C833A53C-4629-48FE-A722-8814F0412C99@gnu.org> (raw)
In-Reply-To: <1907C04E-8C44-424D-B364-6ECD756C0B7C@sanityinc.com>
On October 17, 2017 10:31:56 AM GMT+03:00, Steve Purcell <steve@sanityinc.com> wrote:
> On 17 Oct 2017, at 20:01, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> >> Any idea where that one-column
> >> difference might be coming from?
> >>
> >>
> https://github.com/purcell/page-break-lines/blob/610dbdc9d39a37912e2b8bfbd3e3d15c7e5d622f/page-break-lines.el#L128-L134
> >
> > The space reserved for the continuation glyph? Note that this can
> also happen
> > on GUI frames, if the user disables the fringes.
> >
> > Wouldn't window-text-width suit your needs better?
>
>
> Perhaps, but it returns exactly the same value as window-width in both
> frame types.
>
> Terminal:
>
> window width: 118
> window-width (pix): 118
> window-text-width: 118
> window-text-width (pix): 118
> line-number-display-width: 3
> line-number-display-width (pix): 5
> margins: (nil)
> fringes: (0 0 nil)
> frame-char-width: 1
>
> Graphical window (MacOS):
>
> window width: 203
> window-width (pix): 1421
> window-text-width: 203
> window-text-width (pix): 1421
> line-number-display-width: 3
> line-number-display-width (pix): 35
> margins: (nil)
> fringes: (8 8 nil)
> frame-char-width: 7
Sorry, you are right (too many different functions, all alike). I meant
window-max-chars-per-line.
next prev parent reply other threads:[~2017-10-17 8:15 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
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 [this message]
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=C833A53C-4629-48FE-A722-8814F0412C99@gnu.org \
--to=eliz@gnu.org \
--cc=28248@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--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).