From: Heime <heimeborgia@protonmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Stephen Berman <stephen.berman@gmx.net>, help-gnu-emacs@gnu.org
Subject: Re: New buffer not showing up in Emacs Buffers Menubar
Date: Tue, 24 Sep 2024 13:15:15 +0000 [thread overview]
Message-ID: <7fgpGrWETC1XmAl9Jw5qCspr46SkXdN5srkaubEBAGZhIAye1tc3TlJb3qYiwxVqP6sUuugYg0aiag6IDJAd-Dfjdh4iy4LlOmuFado6B7E=@protonmail.com> (raw)
In-Reply-To: <87frppdytp.fsf@gmail.com>
Sent with Proton Mail secure email.
On Wednesday, September 25th, 2024 at 12:24 AM, Robert Pluim <rpluim@gmail.com> wrote:
> > > > > > On Tue, 24 Sep 2024 13:39:24 +0200, Stephen Berman stephen.berman@gmx.net said:
>
>
> Stephen> It's a user option, so M-x customize-option (or customize-variable) but
>
> Stephen> setq is also fine (in your init file if you want to persist it).
>
>
> In emacs >= 29, `setopt' is the preferred way of setting custom
>
> options in lisp code, since it ensures any custom-set functions are
> run (although for this particular option it doesnʼt matter).
>
> Robert
> --
Although it does not matter, would setopt still be what one should really
use and stick with in a formal manner ?
next prev parent reply other threads:[~2024-09-24 13:15 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
2024-09-24 12:24 ` Robert Pluim
2024-09-24 13:15 ` Heime [this message]
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='7fgpGrWETC1XmAl9Jw5qCspr46SkXdN5srkaubEBAGZhIAye1tc3TlJb3qYiwxVqP6sUuugYg0aiag6IDJAd-Dfjdh4iy4LlOmuFado6B7E=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rpluim@gmail.com \
--cc=stephen.berman@gmx.net \
/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.