Comments on: Editing and testing scripts in SciTE http://blog.dotsmart.net/2007/12/19/editing-and-testing-scripts-in-scite/ insert witty, geeky tagline here... Fri, 03 Feb 2012 22:33:27 +0000 hourly 1 http://wordpress.com/ By: Duncan Smart http://blog.dotsmart.net/2007/12/19/editing-and-testing-scripts-in-scite/#comment-741 Tue, 29 Sep 2009 09:06:57 +0000 http://blog.dotsmart.net/2007/12/19/scite-scintilla-text-editor/#comment-741 Jim, you shouldn’t need to do that if you put the following in your SciTEUser.properties (Options menu > Open User Options file) file:

command.go.*.js=cscript.exe //nologo “$(FilePath)”
command.go.subsystem.*.js=0

]]> By: jim knopf http://blog.dotsmart.net/2007/12/19/editing-and-testing-scripts-in-scite/#comment-738 Mon, 28 Sep 2009 11:22:28 +0000 http://blog.dotsmart.net/2007/12/19/scite-scintilla-text-editor/#comment-738 @rrf
Maybe a little to late, but maybe someone reads this:
You have to type
cscript //H:CScript
in a command prompt (or run as dialog) to change the default script interpreter from wscript to cscript

]]> By: rrf http://blog.dotsmart.net/2007/12/19/editing-and-testing-scripts-in-scite/#comment-55 Sun, 25 May 2008 16:12:53 +0000 http://blog.dotsmart.net/2007/12/19/scite-scintilla-text-editor/#comment-55 Exactly what I needed.. thanks .. I couldn’t figure out how to get the output from my .vbs script into the output window instead of a GUI popup window.. this did the trick..

]]>