[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Windows hook extensions: documentation inconsistent with code

From: Darko Miletic <darko_at_uvcms.com>
Date: 2006-03-26 17:03:56 CEST

Ryan Schmidt wrote:
> 2. Which is the correct extension: ".com" or ".cmd", or are both valid?
> Either the book or the Subversion code or both should be updated
> accordingly.

As of windows NT executable extensions are defined in PATHEXT
environment variable. All extensions defined there will be treated as
executables by OS. Common content of PATHEXT looks like this:

.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

.com extension in general is not used so much these days.
.bat and .cmd are extensions for windows batch files.
vbs, vbe and js, jse are for vb script/javascript files that can be
executed with windows scripting engine.
.wsh/wsf are Windows Script Host control files again related to windows
scripting engine.
So in fact if you need some other scripting language added to shell just
add extension to PATHEXT and assign extension with appropriate executable.

Importance of PATHEXT in fact is big. For example to be able to have
executables with extension cgi and execute them with IIS you must add
.cgi extension to PATHEXT, otherwise it does not work.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Mar 26 17:04:42 2006

This is an archived mail posted to the Subversion Users mailing list.