inkscape: enable command-line support #9797
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
see https://inkscape.org/en/doc/inkscape-man.html **Note:** Running `inkscape` from the command line changes the working directory to `#{staged_path}` (i.e., `/opt/homebrew-cask/Caskroom/inkscape/0.91-1/Inkscape.app`), which means that all file arguments should be given as *absolute paths*. There is a shim script in `Inkscape.app/Contents/Resources/script`, but it doesn't solve this issue any further than simply running `Inkscape.app/Contents/Resources/bin/inkscape`. See also http://wiki.inkscape.org/wiki/index.php/MacOS_X#Inkscape_command_line
|
Cool - thanks for this! |
phinze
added a commit
that referenced
this pull request
Feb 28, 2015
inkscape: enable command-line support
|
Glad to help where I can. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
see https://inkscape.org/en/doc/inkscape-man.html
Note: Running
inkscapefrom the command line changes the workingdirectory to
#{staged_path}(i.e.,/opt/homebrew-cask/Caskroom/inkscape/0.91-1/Inkscape.app), whichmeans that all file arguments should be given as absolute paths.
There is a shim script in
Inkscape.app/Contents/Resources/script,but it doesn't solve this issue any further than simply running
Inkscape.app/Contents/Resources/bin/inkscape.See also http://wiki.inkscape.org/wiki/index.php/MacOS_X#Inkscape_command_line