Command.unshift producing strange command about grim

[jonmagic]

The last time I touched that line was here I think: 3671c1d

Then you have these commits that change it:
7fa3eab#diff-acd95e3665359bdb0f9e7518583032c2
d8a21bc#diff-acd95e3665359bdb0f9e7518583032c2

Do you think you could write a failing test that displays the issue you described?

[rubikan]

I created a gist since I didn't want to commit and push a failing test ;)

https://gist.github.com/Rubikan/47e78c147d7a1d93ac8b

I tried it on Mac OSX (created a symlink to gs named gstest) and Windows, but it only failed on Windows.
The error I get looks like this:
Errno::ENOENT: No such file or directory - PATH=.:###########

Instead of the hashes it prints out my whole PATH (or big chunks of it, I didn't check the whole thing)

[gordcorp]

FYI I have the same problem on windows, I fixed it by commenting out that line. With ImageMagick convert and ghostscript on my path, I just had to set the processor with Grim.processor = Grim::ImageMagickProcessor.new({:ghostscript_path => "gswin64c.exe"})
The better fix would be modifying the PATH var in an OS-agnostic way, but that's beyond my Ruby-fu.
Thanks for your work, I'm finding this project useful.

[jonmagic]

@BJgordon thanks for the report and sorry for the late reply. Definitely sounds like this could be handled better. I don't run windows so I'm kind of hoping someone else will figure it out on windows and submit a PR and then I can test it against osx and linux ✨

[jonmagic]

This should be resolved by #27 now.