From: "Eli Zaretskii" <eliz@elta.co.il>
Subject: Re: OT: Run Ant in MingW shell?
Date: Fri, 17 Oct 2003 08:28:33 +0200 [thread overview]
Message-ID: <6654-Fri17Oct2003082833+0200-eliz@elta.co.il> (raw)
In-Reply-To: <86vfqoyld9.fsf@slowfox.dyndns.org> (message from Kai Grossjohann on Thu, 16 Oct 2003 22:32:18 +0200)
> From: Kai Grossjohann <kai.grossjohann@gmx.net>
> Newsgroups: gnu.emacs.help
> Date: Thu, 16 Oct 2003 22:32:18 +0200
>
> > The shell cannot know that a file foo.bat
> > needs to be run thru "cmd /c", so it's your responsibility to type
> > that on the command line.
>
> Why can't the shell know? In a Windows environment, it seems useful
> to just tell it so.
That means someone should hack the Bash sources to add the code to do
this. Originally, Bash simply looks at the executable bit returned by
`stat' and at the magic number. If the magic number is "#!", it then
reads the first line of the script looking for the interpreter.
(Actually, I think this is in the kernel, at least on some flavors of
Unix.)
> (Actually, there must be a registry of some kind in Windows that
> says that *.bat files are associated with cmd, but I don't know the
> details.)
No, AFAIK the association of *.bat files in inside CMD itself, not in
the registry.
next prev parent reply other threads:[~2003-10-17 6:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 8:18 OT: Run Ant in MingW shell? Kai Grossjohann
2003-10-09 11:05 ` Eli Zaretskii
[not found] ` <mailman.1406.1065699895.21628.help-gnu-emacs@gnu.org>
2003-10-14 22:24 ` Kai Grossjohann
2003-10-15 5:49 ` Eli Zaretskii
2003-10-17 15:50 ` Kai Grossjohann
2003-10-15 11:07 ` Kai Grossjohann
2003-10-16 6:38 ` Eli Zaretskii
[not found] ` <mailman.1779.1066286649.21628.help-gnu-emacs@gnu.org>
2003-10-16 20:32 ` Kai Grossjohann
2003-10-17 6:28 ` Eli Zaretskii [this message]
[not found] ` <mailman.1848.1066372440.21628.help-gnu-emacs@gnu.org>
2003-10-17 7:19 ` Jason Rumney
2003-10-15 17:04 ` Paul Kinnucan
2003-10-15 19:27 ` Kai Grossjohann
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=6654-Fri17Oct2003082833+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
/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.
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).