From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#28248: 26.0.50; display-line-numbers does not affect window-width / window-text-width Date: Tue, 17 Oct 2017 11:23:56 +0300 Message-ID: <785ae770-ea0a-ec74-c986-fde32a48ab0f@yandex.ru> References: <834lst5bep.fsf@gnu.org> <83d15mfqoj.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1508228735 15186 195.159.176.226 (17 Oct 2017 08:25:35 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 17 Oct 2017 08:25:35 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Thunderbird/56.0 Cc: steve@sanityinc.com, 28248@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Oct 17 10:25:25 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e4NBT-0000BL-Gb for geb-bug-gnu-emacs@m.gmane.org; Tue, 17 Oct 2017 10:25:07 +0200 Original-Received: from localhost ([::1]:37163 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e4NBZ-0002ar-8y for geb-bug-gnu-emacs@m.gmane.org; Tue, 17 Oct 2017 04:25:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59374) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e4NBR-0002al-Oi for bug-gnu-emacs@gnu.org; Tue, 17 Oct 2017 04:25:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e4NBN-0005qi-Tl for bug-gnu-emacs@gnu.org; Tue, 17 Oct 2017 04:25:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:36117) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e4NBN-0005qQ-QL for bug-gnu-emacs@gnu.org; Tue, 17 Oct 2017 04:25:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e4NBN-0000jy-LF for bug-gnu-emacs@gnu.org; Tue, 17 Oct 2017 04:25:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 17 Oct 2017 08:25:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 28248 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 28248-submit@debbugs.gnu.org id=B28248.15082286472779 (code B ref 28248); Tue, 17 Oct 2017 08:25:01 +0000 Original-Received: (at 28248) by debbugs.gnu.org; 17 Oct 2017 08:24:07 +0000 Original-Received: from localhost ([127.0.0.1]:44798 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e4NAV-0000il-4T for submit@debbugs.gnu.org; Tue, 17 Oct 2017 04:24:07 -0400 Original-Received: from mail-wm0-f53.google.com ([74.125.82.53]:45490) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e4NAT-0000iF-PT for 28248@debbugs.gnu.org; Tue, 17 Oct 2017 04:24:06 -0400 Original-Received: by mail-wm0-f53.google.com with SMTP id q124so2152132wmb.0 for <28248@debbugs.gnu.org>; Tue, 17 Oct 2017 01:24:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=4CEebhl2RBMXiAj7fqUOEW6GKTI7xHzDfwAB8Jqe8l8=; b=Klf57hc9KStjXZ3MgocaTWs7ij+kebYq0hl1+QeT/kpVI4ze+s8BXI7eg4J+acfABm fb/rUqBYq/8So4VNrX62YGlMp2cVYEeIb4Ws5zyx/i7tlGaVKgI5zMkEw8eNBTX4pRSL nUyUqFFWx6chXNfNREyru1amSFkHUBd0yA6cdzBccDHCpGQkYMx/bqrwa6knvuC7fI/4 i1DQM0BdBgH1KFCjTz5zsfKbnJHuI/75PHcM7j9DHIh80sOUlW/DNc2uObKD9cso0F6v JH2VnqaP2o0knjA7+ZUVC/VOArTlX4BHfaUMnwUNrT5dt+OgRzrZE1c9/n6y+daz835j 13pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=4CEebhl2RBMXiAj7fqUOEW6GKTI7xHzDfwAB8Jqe8l8=; b=q/TYtKf+4ZrrC5/AC3NXWBYGiz5CE+8irB0P8Dg4tU2Sq1e52UOygo9snFOo4a96Nr Xuzcj5iRQ4YXAL2/ar3WzNEXs8jbc3BuqMIiX3kHGVY9JTCMT1rxaxoInxKn/aiZvmRV Lmnl5Y0RuS4ULI2wC8vzY4vP48+xjSZ4MUq343xQtUfOu7lWAkgh5DRWxqNC+9y/pqii uRcWG1Jw5k/zbBpPirhZS1WK1fA4sQeBMvWdyjK3omp2AgoRPr6iSYLROzgbgxjgPEy8 Js+kMYjyWKQ6BA219tvU15C8D3+kM7ppbEV7mymLce+TMzt6ozn8qwTfc801E2CdKqO3 t11g== X-Gm-Message-State: AMCzsaXG1igdUP3mZzX5qgUtn1qWH7Cq9iS5lzt3oWT0zXzJ57zr+PBx tNSRsUQBhcaGI3VVbG4wsAypb81X X-Google-Smtp-Source: AOwi7QAqjOIeSLTnmfDLciUlC2Wmtl2epgtLtBOgp1qz+GwJ7YFvH3MR/JxztdbvIzESqeVhp377pg== X-Received: by 10.80.243.12 with SMTP id p12mr16125306edm.38.1508228639848; Tue, 17 Oct 2017 01:23:59 -0700 (PDT) Original-Received: from [192.168.1.3] ([185.105.174.193]) by smtp.googlemail.com with ESMTPSA id q16sm7128017eda.87.2017.10.17.01.23.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Oct 2017 01:23:58 -0700 (PDT) In-Reply-To: <83d15mfqoj.fsf@gnu.org> Content-Language: en-US X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:138591 Archived-At: On 10/17/17 5:34 AM, Eli Zaretskii wrote: >> Should I always use (+ 2 (line-number-display-width)) instead? > > If you need it in columns, yes. This is for consistency with the > value of display-line-numbers-width, which you can set. > >> 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? > > As long as we don't change the implementation, yes. Alternatively, > you can call line-number-display-width with the optional argument and > get the result in pixels, in which case it includes everything (you > can divide by frame-char-width to get the result back in columns). Thanks, but isn't that more inconsistent? I would expect both return values of this function to measure the same thing, and there's nothing in the docstring to explain that difference. On the other hand, the return value of the function can differ from what a variable is set to. I guess I could live with that, but the function's docstring needs updating.