unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: luangruo@yahoo.com, 64398@debbugs.gnu.org, angelo.borsotti@gmail.com
Subject: bug#64398: Buffer list
Date: Thu, 05 Oct 2023 19:05:31 +0300	[thread overview]
Message-ID: <835y3l3vhw.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkB9kxB2Rge_21MtOSjh6AGS_qwq_0JUmGBC_MzxRY9OQ@mail.gmail.com> (message from Stefan Kangas on Thu, 5 Oct 2023 12:54:02 +0000)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 5 Oct 2023 12:54:02 +0000
> Cc: 64398@debbugs.gnu.org, angelo.borsotti@gmail.com
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> This doesn't work because menu-bar.el is preloaded and additionally
> >> because Emacs supports creating both GUI and terminal frames in the same
> >> process, whereas a feature can only be loaded once, with the value of
> >> display-graphic-p subject to whatever frame is selected at the time it
> >> is loaded.  Why not set it to 15 and call it a day?
> >
> > It's possible, but then we will not be able to extend this in the
> > future anymore, as I explained above.  But maybe we don't care.
> >
> > If we do care, then we could have an additional option, or we could
> > make this option accept a cons cell, or something else.
> 
> If we know that it will work, perhaps the simplest solution here is
> fine, and we can just bump the default to 15 unconditionally.

Fine, let's go by that for now, and revisit it if and when it becomes
an issue.  But please add a comment there saying that going much
further than 15 should consider the height of TTY frames.





  reply	other threads:[~2023-10-05 16:05 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
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 [this message]
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

  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=835y3l3vhw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64398@debbugs.gnu.org \
    --cc=angelo.borsotti@gmail.com \
    --cc=luangruo@yahoo.com \
    --cc=stefankangas@gmail.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).