From: CToID <funk443@yahoo.com.tw>
To: help-gnu-emacs@gnu.org
Subject: Re: Question about initial-buffer-choice
Date: Fri, 12 Jul 2024 23:27:34 +0800 [thread overview]
Message-ID: <27a8a4a1-6d00-40c5-b23f-16fc749fa856@yahoo.com.tw> (raw)
In-Reply-To: <86ikxalkle.fsf@gnu.org>
On 2024-07-12 Fri 23:02 UTC+0800, Eli Zaretskii <eliz@gnu.org> said:
>
> When this variable is non-nil, its value is handled as an additional
> command-line argument. So yes, this is the intended behavior when you
> start Emacs with names of files or directories from the command line.
>
Myabe it's better to add another variable to control this behaviour?
--
Best,
ID
next prev parent reply other threads:[~2024-07-12 15:27 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 [this message]
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
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=27a8a4a1-6d00-40c5-b23f-16fc749fa856@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).