From: CToID <funk443@yahoo.com.tw>
To: help-gnu-emacs@gnu.org
Subject: Re: Question about initial-buffer-choice
Date: Sat, 13 Jul 2024 15:24:34 +0800 [thread overview]
Message-ID: <9a9aabd6-805d-4284-a3c6-c990c18d3e7b@yahoo.com.tw> (raw)
In-Reply-To: <86le25x0pd.fsf@gmail.com>
On 2024-07-13 14:31 GMT+08:00, Joel Reicher wrote:
>
> I get behaviour similar to what I think you want by always using
> emacsclient to open files, and including --no-splash in the command for
> alternate editor.
>
I did some testing, and --no-splash only decides whether Emacs shows the
splash buffer or not. It doesn't affect the buffer specified in
initial-buffer-choice.
--
Best,
ID
next prev parent reply other threads:[~2024-07-13 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2829dbca-971f-4da5-885a-29afce1dbbb1.ref@yahoo.com.tw>
2024-07-12 13:24 ` Question about initial-buffer-choice CToID
2024-07-12 15:02 ` Eli Zaretskii
2024-07-12 15:27 ` CToID
2024-07-12 16:06 ` Eli Zaretskii
2024-07-12 17:02 ` CToID
2024-07-12 17:45 ` Eli Zaretskii
2024-07-13 6:31 ` Joel Reicher
2024-07-13 7:24 ` CToID [this message]
2024-07-13 7:54 ` Joel Reicher
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=9a9aabd6-805d-4284-a3c6-c990c18d3e7b@yahoo.com.tw \
--to=funk443@yahoo.com.tw \
--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.
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).