unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, 7784@debbugs.gnu.org, sds@gnu.org
Subject: bug#7784: executable-find does not find scripts on woe32
Date: Thu, 06 Jan 2011 07:13:25 +0800	[thread overview]
Message-ID: <87d3obeyga.fsf@gnu.org> (raw)
In-Reply-To: <83vd23mi5s.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 Jan 2011 18:25:51 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Óscar Fuentes <ofv@wanadoo.es>
>> Cc: Sam Steingold <sds@gnu.org>, 7784@debbugs.gnu.org
>> Date: Wed, 05 Jan 2011 15:24:26 +0100
>> 
>> One thing I noticed while experimenting with file-executable-p is that
>> it returns false for files with extensions listed in PATHEXT. For
>> instance, .JS is listed on one machine's PATHEXT but, after creating
>> foo.js, (file-executable-p "foo.js") returns nil.
>> 
>> As those files are directly executable from the shell, maybe Emacs
>> should recognize them as executables as well?
>
> Patches for supporting PATHEXT are most welcome, TIA.

It might also be a good idea to merge the list used by is_exec in w32.c
with the list that is used as the initial value of exec-suffixes.





  reply	other threads:[~2011-01-05 23:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 23:44 bug#7784: executable-find does not find scripts on woe32 Sam Steingold
2011-01-05  1:18 ` Óscar Fuentes
2011-01-05  4:05   ` Sam Steingold
2011-01-05 11:26     ` Eli Zaretskii
2011-01-05 14:24       ` Óscar Fuentes
2011-01-05 16:25         ` Eli Zaretskii
2011-01-05 23:13           ` Jason Rumney [this message]
2011-01-05 14:40       ` Sam Steingold
2011-01-05 16:24         ` Eli Zaretskii
2011-01-05 11:30   ` Eli Zaretskii
2011-01-05  7:14 ` Jason Rumney

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=87d3obeyga.fsf@gnu.org \
    --to=jasonr@gnu.org \
    --cc=7784@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=ofv@wanadoo.es \
    --cc=sds@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).