From: "Clément Pit--Claudel" <clement.pitclaudel@live.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 25671@debbugs.gnu.org
Subject: bug#25671: Feature request: emacs -Q --script as a single binary
Date: Fri, 10 Feb 2017 15:21:15 -0500 [thread overview]
Message-ID: <bdb3893f-688a-c56b-28eb-4d5c447fd3ed@live.com> (raw)
In-Reply-To: <05d1eqost8.fsf@fencepost.gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 577 bytes --]
On 2017-02-10 12:32, Glenn Morris wrote:
> Clément Pit--Claudel wrote:
>
>>>> What about providing elisp or emacs-script as a separate binary?
>>>
>>> What about it?
>>
>> Would that be OK?
>
> I would not like installing Emacs to pollute my PATH with trivial things
> like that. In https://debbugs.gnu.org/20682#11 I mentioned a
> standard solution for this issue as used by perl, ruby, etc;
> namely a -x switch.
Can you explain how that works wrt the problem I mentioned in my original post? "#!/usr/bin/env emacs -x" doesn't work, does it?
Clément
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-02-10 20:21 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
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 [this message]
-- 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
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=bdb3893f-688a-c56b-28eb-4d5c447fd3ed@live.com \
--to=clement.pitclaudel@live.com \
--cc=25671@debbugs.gnu.org \
--cc=rgm@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.
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).