unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Andrew L. Moore" <slewsys@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: executable-set-magic update
Date: Sat, 22 Jul 2017 10:36:27 +0300	[thread overview]
Message-ID: <83h8y4apok.fsf@gnu.org> (raw)
In-Reply-To: <AC06BE06-66BB-448B-B102-005B4336723A@gmail.com> (slewsys@gmail.com)

> From: "Andrew L. Moore" <slewsys@gmail.com>
> Date: Sat, 10 Jun 2017 15:31:04 -0400
> Cc: emacs-devel@gnu.org
> 
> > On Jun 10, 2017, at 3:17 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > 
> >> From: "Andrew L. Moore" <slewsys@gmail.com>
> >> Date: Fri, 9 Jun 2017 17:31:30 -0400
> >> 
> >> lisp/progmodes/executable.el does not appear to support magic numbers of the form `#/usr/bin/env interpreter’.  One way to extend support is via the attached diff which merely adds a new variable `executable-interpreter-path-absolute’.  Set the new variable to nil and variable `executable-prefix’ to “#!/usr/bin/env “.
> > 
> > Thanks.
> > 
> > Wouldn't it be more elegant (and perhaps also safer, security-wise) if
> > we supported the special prefix "/usr/bin/env" directly, i.e. without
> > feeding it via some kind of "back door", and allowing arbitrary
> > strings there?
> 
> Attached below is a patch following your suggestions. From NEWS:

Thanks, pushed to master.

With this contribution, you've exhausted the amount of changes we can
accept without legal papers, so I'd encourage you to start the
paperwork rolling, for us to be able to accept further contributions.



  reply	other threads:[~2017-07-22  7:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09 21:31 executable-set-magic update Andrew L. Moore
2017-06-10  7:17 ` Eli Zaretskii
2017-06-10 19:31   ` Andrew L. Moore
2017-07-22  7:36     ` Eli Zaretskii [this message]
2017-06-10 12:26 ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2017-07-24 18:22 Andrew L. Moore
2017-07-24 22:41 ` Andrew L. Moore

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=83h8y4apok.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=slewsys@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).