This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: *.COM file execution
- To: "Dr. Volker Zell" <vzell at de dot oracle dot com>
- Subject: Re: *.COM file execution
- From: Pavel Tzekov <paveltz at csoft dot bg>
- Date: Fri, 11 Sep 1998 16:13:32 +0300
- CC: noer at cygnus dot com, gnu-win32 at cygnus dot com
- Organization: CSoft Ltd.
- References: <3801-Thu10Sep1998164708+0200-vzell@de.oracle.com>
- Reply-To: paveltz at csoft dot bg
Dr. Volker Zell wrote:
>
> Hi
>
> >> The necessary support in Cygwin32 is fixed in the development
> >> sources / next major release:
>
> >> * spawn.cc (perhaps_suffix): If report_failure_p is
> >> non-zero this function will search for (PROG is the pathname to
> >> the executable file) PROG.exe, PROG, PROG.com, PROG.bat, and
> >> PROG.cmd and return either the full path name if found or NULL
> >> if not. (spawn_guts): If the file name of the executable end
> >> in either .exe, .com, .bat, or .cmd we assume that it is not a
> >> script file and therefore do not open the file to determine if
> >> it is.
>
> Is it possible to include the .btm extension for the 4NT command
> interpreter fans. Here the description of a btm file from the
> online-help of the 4NT command interpreter:
>
> BTM File: A special type of 4NT batch file which is loaded into memory to speed up execution.
Wouldn't that make it neccessary to add support in the bash sources for
4NT ?
*.BTM files are not plain *.BAT files
Pavel Tzekov
CSoft Ltd.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".