From 9c534cd4ab986874e52f6bfb34e93e9266ea0c1c Mon Sep 17 00:00:00 2001 From: Ingmar Steiner Date: Fri, 27 Feb 2015 10:36:29 +0100 Subject: [PATCH] inkscape: enable command-line support 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 --- Casks/inkscape.rb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Casks/inkscape.rb b/Casks/inkscape.rb index 70f5ba5efd00b..e22b127a83574 100644 --- a/Casks/inkscape.rb +++ b/Casks/inkscape.rb @@ -8,6 +8,8 @@ license :gpl app 'Inkscape.app' + # NOTE: running inkscape on the command line requires absolute paths to files + binary 'Inkscape.app/Contents/Resources/bin/inkscape' zap :delete => '~/.inkscape-etc'