![\"SNAGHTMLef89bd\"](\"http:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2011\/09\/SNAGHTMLef89bd.png\" "\\"SNAGHTMLef89bd\\"")
<\/a><\/p>\nBecause some of you asked nicely, we also added SQL and Python to the languages supported by PrimalPad’s syntax coloring.<\/p>\n
Last but not least, you can now run your script files from within PrimalPad. While it doesn’t have PrimalScript’s output capture abilities, it still works pretty well for some quick hit and run scripting.<\/p>\n
<\/p>\n
The tools menu is where you make it all happen. By setting up PowerShell and CMD.exe properly you can run your scripts and see their output too.
Don’t worry, it’s easy; just a few steps.<\/p>\n
Here are the settings for PowerShell and VBScript respectively:<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
You can probably guess that the the $File$ parameter gets replaced with the path of whatever file is currently active. You can also use $FileTitle$ if you just want the base name of the file. So “C:\\users\\somename\\My Documents\\Script\\drivespace.ps1” would result in “drivespace”. Make sure to enclose the $File$ parameter in quotes, otherwise pathnames with spaces in them will just throw an error.<\/p>\n
The command windows stay open with the output of your script because of the \u2013noexit<\/em> parameter for PowerShell and the \/K<\/em> parameter for CMD.exe.<\/p>\n Oh and in case you wondered, PrimalPad still needs no installation, still comes in 32 and 64 bit versions and it’s still free.<\/p>\n