From: Stephen Berman <stephen.berman@gmx.net>
To: Heime <heimeborgia@protonmail.com>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: New buffer not showing up in Emacs Buffers Menubar
Date: Tue, 24 Sep 2024 13:39:24 +0200 [thread overview]
Message-ID: <875xqlmf93.fsf@gmx.net> (raw)
In-Reply-To: <kFPSQqrDX0A4-xV0dYvVRc4CIjtzAYgtSK_2mY3HKNBRuTgnG9Ek-2DGgXiki7g9kyZuBfPMf0abZbOIau_ANoFn75PkECI-0OxX9GSl6_0=@protonmail.com> (Heime's message of "Tue, 24 Sep 2024 11:32:57 +0000")
[resending because I mistakenly omitted the list address]
On Tue, 24 Sep 2024 11:32:57 +0000 Heime <heimeborgia@protonmail.com> wrote:
[...]
>> > Is there always a requirement to instruct pop-to-buffer, view-buffer,
>> > display-buffer, switch-to-buffer and display-like commands so that a
>> > new buffer gets shown.
>>
>>
>> If you mean the buffer names being displayed in the Buffers menu, no, that
>> should be automatic for the most recent buffers up to buffers-menu-max-size.
>>
>> Steve Berman
>
> And the older ones would be removed from view ? Hew does one set
> buffers-menu-max-size ? With a setq as (setq buffers-menu-max-size new-size)
> or with a different command ?
It's a user option, so M-x customize-option (or customize-variable) but
setq is also fine (in your init file if you want to persist it).
Steve Berman
next prev parent reply other threads:[~2024-09-24 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 22:25 New buffer not showing up in Emacs Buffers Menubar Heime
2024-09-24 7:41 ` Stephen Berman
2024-09-24 8:19 ` Heime
2024-09-24 8:34 ` Stephen Berman
2024-09-24 10:00 ` Heime
2024-09-24 10:39 ` Stephen Berman
2024-09-24 11:32 ` Heime
2024-09-24 11:39 ` Stephen Berman [this message]
2024-09-24 12:24 ` Robert Pluim
2024-09-24 13:15 ` Heime
2024-09-24 13:22 ` Robert Pluim
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=875xqlmf93.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@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.