all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jidanni@jidanni.org, 30692@debbugs.gnu.org
Subject: bug#30692: list-buffers has hardwired 80 character width from the 80's
Date: Fri, 07 Aug 2020 14:19:32 +0200	[thread overview]
Message-ID: <87eeoi7inf.fsf@gnus.org> (raw)
In-Reply-To: <83v9hu7j42.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 07 Aug 2020 15:09:33 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> It wouldn't change how the file name is displayed at all -- it would
>> continue to be truncated by the window width (i.e., it "pokes out").
>> 
>> As the "formula" today is that the file name takes about half the window,
>> my proposed change would continue to keep that ratio (at least).  That
>> is, if you make the window 100 characters wide, the buffer name would
>> grow from 19 to...  (let's see)...  25-ish, and the file's visible area
>> would increase from 40-ish to 55-ish.
>
> So, as one makes the window wider, instead of using the additional
> space to display more of the file name, we will use it to display more
> of the buffer name?

No, in my calculations above, we increase the width by 20 columns, and
give 5 to the buffer name and 15 to the file name.  (Ish.)

> Even if none of the buffer names is truncated?

No, like I said in the first mail -- it won't be increased beyond the
length of the longest item in the buffer name column.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-08-07 12:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03 23:12 bug#30692: list-buffers has hardwired 80 character width from the 80's 積丹尼 Dan Jacobson
2018-03-04  3:40 ` Eli Zaretskii
2018-03-05  0:23   ` 積丹尼 Dan Jacobson
2018-03-05  3:35     ` Eli Zaretskii
2018-04-14 19:23 ` Lars Ingebrigtsen
2018-04-15 10:35   ` 積丹尼 Dan Jacobson
2018-04-15 12:43     ` Lars Ingebrigtsen
2020-08-07  9:03       ` Lars Ingebrigtsen
2020-08-07  9:08         ` Robert Pluim
2020-08-07 11:44         ` Eli Zaretskii
2020-08-07 11:51           ` Lars Ingebrigtsen
2020-08-07 12:09             ` Eli Zaretskii
2020-08-07 12:19               ` Lars Ingebrigtsen [this message]
2020-08-07 13:54                 ` Eli Zaretskii
2020-08-08  9:39                   ` Lars Ingebrigtsen
2020-08-08  9:50                     ` Eli Zaretskii
2020-08-08 10:13                     ` Basil L. Contovounesios
2020-08-08 10:23                       ` Eli Zaretskii
2020-08-08 10:28                         ` Lars Ingebrigtsen
2020-08-08 10:41                           ` Eli Zaretskii
2020-08-08 10:59                             ` Lars Ingebrigtsen
2020-08-08 10:30                       ` Lars Ingebrigtsen
2020-08-08 10:37                         ` Basil L. Contovounesios
2020-08-08 11:02                           ` Lars Ingebrigtsen

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=87eeoi7inf.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=30692@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jidanni@jidanni.org \
    /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.