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 20:53:36 +0300 [thread overview]
Message-ID: <864j8nhplr.fsf@gnu.org> (raw)
In-Reply-To: <87h6coasly.fsf@> (message from Björn Bidar on Wed, 17 Jul 2024 19:30:33 +0300)
> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: funk443@yahoo.com.tw, stefankangas@gmail.com, acorallo@gnu.org,
> 72089@debbugs.gnu.org
> Date: Wed, 17 Jul 2024 19:30:33 +0300
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I don't really see a big difference, since we have --eval.
>
> Passing elisp to commands in a shell script is pain
Not when all you need to do is a single setq.
> and command line flags are visible in --help.
So is --eval.
Adding a new command-line option also has downsides: it's another
thing to learn and remember. "emacs --help" already shows more than
60 different options, and I personally sometimes have hard time
finding the option whose exact name I happened to forget in this very
long list. So adding one more option doesn't come for free.
prev parent reply other threads:[~2024-07-17 17:53 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
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 [this message]
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=864j8nhplr.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).