all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64398@debbugs.gnu.org, angelo.borsotti@gmail.com
Subject: bug#64398: Buffer list
Date: Tue, 5 Sep 2023 14:46:32 -0700	[thread overview]
Message-ID: <CADwFkmkdeo+Q3Ar+XF+h9EF0RRfsthHab1cot_twa4jHeJOTGw@mail.gmail.com> (raw)
In-Reply-To: <83sf7t4aic.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> If we make the number much larger, we should probably have a separate
> default value for TTY frames, where I think small frame sizes are
> still quite frequent.

Agreed.

> Or maybe we should have the default computed dynamically based on the
> actual frame size?

That's an interesting idea, but would be more work, and we have other
things to do too.  It also somehow seems to be the job of the toolkit to
worry about such things, but maybe that's just me.

It's tempting to just bump this to some similarly conservative value
like 15 or 12 on graphical displays, and be done with it.





  reply	other threads:[~2023-09-05 21:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-01 10:31 bug#64398: Buffer list Angelo Borsotti
2023-07-01 10:44 ` Eli Zaretskii
2023-09-04 20:22   ` Stefan Kangas
2023-09-05  2:30     ` Eli Zaretskii
2023-09-05 21:46       ` Stefan Kangas [this message]
2023-09-06 11:25         ` Eli Zaretskii
2023-09-06 11:54           ` Stefan Kangas
2023-09-06 12:39             ` Eli Zaretskii
2023-09-30 23:09               ` Stefan Kangas
2023-10-05  7:21             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-05  8:10               ` Eli Zaretskii
2023-10-05 12:54                 ` Stefan Kangas
2023-10-05 16:05                   ` Eli Zaretskii
2023-10-05 18:19                     ` Stefan Kangas

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=CADwFkmkdeo+Q3Ar+XF+h9EF0RRfsthHab1cot_twa4jHeJOTGw@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=64398@debbugs.gnu.org \
    --cc=angelo.borsotti@gmail.com \
    --cc=eliz@gnu.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.