I noticed that when you try and use verbose on an image with spaces in its name, or technically anywhere within its path, that it would throw an error. Like so:
** (MatchError) no match of right hand side value: {"mogrify: unable to open image `/home/username/dir/mogrify/test/fixtures/ben\\': No such file or directory @ error/blob.c/OpenBlob/2712.\nmogrify: no decode delegate for this image format `' @ error/constitute.c/ReadImage/501.\nmogrify: unable to open image `der.jpg': No such file or directory @ error/blob.c/OpenBlob/2712.\n", 1}
I added a test in the repo where you simply try to call verbose on the @fixture_with_space variable and it fails. I am preparing a PR to fix this.
The issue falls with the ~w() function call, you are passing in the path/file name and substituting spaces with "// " but that does not properly sanitize the string to work with the ~w() function
Will link it here soon. It will also update all functions that use anything that could have a space, also will be updating tests as well.
I noticed that when you try and use
verbose
on an image with spaces in its name, or technically anywhere within its path, that it would throw an error. Like so:** (MatchError) no match of right hand side value: {"mogrify: unable to open image `/home/username/dir/mogrify/test/fixtures/ben\\': No such file or directory @ error/blob.c/OpenBlob/2712.\nmogrify: no decode delegate for this image format `' @ error/constitute.c/ReadImage/501.\nmogrify: unable to open image `der.jpg': No such file or directory @ error/blob.c/OpenBlob/2712.\n", 1}
I added a test in the repo where you simply try to call verbose on the
@fixture_with_space
variable and it fails. I am preparing a PR to fix this.The issue falls with the
~w()
function call, you are passing in the path/file name and substituting spaces with "// " but that does not properly sanitize the string to work with the~w()
functionWill link it here soon. It will also update all functions that use anything that could have a space, also will be updating tests as well.