From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit--Claudel" <clement.pitclaudel@live.com>
Cc: 25671@debbugs.gnu.org
Subject: bug#25671: Feature request: emacs -Q --script as a single binary
Date: Fri, 10 Feb 2017 18:58:29 +0200 [thread overview]
Message-ID: <83shnm2dai.fsf@gnu.org> (raw)
In-Reply-To: <fe59c761-3751-1ae9-c178-2b51fd550e04@live.com> (message from Clément Pit--Claudel on Fri, 10 Feb 2017 11:45:55 -0500)
> Cc: 25671@debbugs.gnu.org
> From: Clément Pit--Claudel <clement.pitclaudel@live.com>
> Date: Fri, 10 Feb 2017 11:45:55 -0500
>
> >>> I believe changing the program behavior depending on how it was named
> >>> in the command that invoked it is against GNU coding standards.
> >>
> >> What about providing elisp or emacs-script as a separate binary?
> >
> > What about it?
>
> Would that be OK? Could it work?
Yes, it will. Although distributing two large binaries might be
overkill. (All that just to make shell scripts slightly simpler?)
next prev parent reply other threads:[~2017-02-10 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 21:14 bug#25671: Feature request: emacs -Q --script as a single binary Clément Pit--Claudel
2017-02-09 21:27 ` Glenn Morris
2017-02-09 21:32 ` Clément Pit--Claudel
2017-02-10 7:37 ` Eli Zaretskii
2017-02-10 14:17 ` Clément Pit--Claudel
2017-02-10 15:02 ` Eli Zaretskii
2017-02-10 16:45 ` Clément Pit--Claudel
2017-02-10 16:58 ` Eli Zaretskii [this message]
2017-02-10 20:21 ` Clément Pit--Claudel
2017-02-10 17:32 ` Glenn Morris
2017-02-10 20:21 ` Clément Pit--Claudel
-- strict thread matches above, loose matches on Subject: below --
2015-05-28 13:57 bug#20682: 25.0.50; Enable users to combine --script and --quick Michael Heerdegen
2015-05-28 18:48 ` Stefan Monnier
2015-05-28 20:30 ` Glenn Morris
2022-04-18 11:01 ` bug#20682: bug#25671: Feature request: emacs -Q --script as a single binary Lars Ingebrigtsen
2022-05-05 22:14 ` Michael Heerdegen
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=83shnm2dai.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25671@debbugs.gnu.org \
--cc=clement.pitclaudel@live.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.