-
Notifications
You must be signed in to change notification settings - Fork 0
macosx
Since version 0.5.2 the run editor dialog automatically fills the path field with /usr/bin/open
and set correctly the parameters, user no longer needs to make the manual configuration shown below.
Since version 0.0.8.2 it is possible to pass command line arguments to editors.
Under MacOSX this feature required radical changes on code due to a bug present on all Mozilla applications. Many users suggest solutions and workarounds and here you find them.
Stefan Nowak says: "Simply use '/usr/bin/open' available in all OSX versions (as far as I know and as far as the manpage says)."
To successfully view your HTML page source code in other apps, set this in VSW:
Editor Path : /usr/bin/open
Parameters : -a /path/to/your.app $f
Direct binary targeting is especially inflexible if you have FAT binaries (intel and ppc), therefore targeting '.app' is highly recommended.
Target '.app' and let the system decides which binary to start.
Tim Wood shows us how to use open
to succefully use ViewSourceWith with TextWrangler and Dreamweaver
Editor Path : /usr/bin/open
Parameters : -a /path/to/TextWrangler.app $f
Editor Path : /usr/bin/open
Parameters : -a /path/to/Dreamweaver\ 8 $f
I'm not sure why DreamWeaver doesn't require the .app at the end of the application name. It must be a Macromedia thing ;-)
It's worth noting that this approach will solve the opening multiple copies of an app problem.
Editor Path : /usr/bin/open
Parameters : -a /path/to/Dreamweaver.app $f
Editor Path : /Applications/TextMate.app/Contents/Resources/mate
You can find more details here
This solution was suggested to me by Leigh.
You can use launch application that allows to run app bundles from command line.
For example to have only one TextEdit instance you can specify:
Editor Path : /usr/bin/launch
Parameters : /Applications/TextEdit.app $f