From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: acorallo@gnu.org, funk443@yahoo.com.tw, 72089@debbugs.gnu.org,
stefankangas@gmail.com
Subject: bug#72089: [PATCH] Option to control Emacs' behaviour when invoked with file args.
Date: Wed, 17 Jul 2024 14:24:47 +0300 [thread overview]
Message-ID: <86h6cogt1c.fsf@gnu.org> (raw)
In-Reply-To: <87sew9asat.fsf@> (message from Björn Bidar on Wed, 17 Jul 2024 01:24:58 +0300)
> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: CToID <funk443@yahoo.com.tw>, Stefan Kangas <stefankangas@gmail.com>,
> Andrea Corallo <acorallo@gnu.org>, 72089@debbugs.gnu.org
> Date: Wed, 17 Jul 2024 01:24:58 +0300
>
> I wonder if it would make more sense that this should be command line
> flag or a default rather that an option.
>
> An option would require the user to set the option while a command line
> flag would make the option redundant and more flexible.
> The option would also allow the user to call a mode like e.g. Magit
> use the mode and then close the frame without the initial buffer.
>
> A default would be more intuitive as Emacs would behave pretty much like
> any other editor out there.
I don't really see a big difference, since we have --eval.
next prev parent reply other threads:[~2024-07-17 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32450bf6-4672-4357-8632-a536c774b6ab.ref@yahoo.com.tw>
2024-07-12 19:18 ` bug#72089: [PATCH] Option to control Emacs' behaviour when invoked with file args CToID via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-13 6:19 ` Eli Zaretskii
2024-07-13 7:59 ` Andrea Corallo
2024-07-16 22:24 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87sew9asat.fsf@>
2024-07-17 6:29 ` CToID via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-17 11:24 ` Eli Zaretskii [this message]
2024-07-17 16:30 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87h6coasly.fsf@>
2024-07-17 17:53 ` Eli Zaretskii
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=86h6cogt1c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72089@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=funk443@yahoo.com.tw \
--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 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.