Scoop: ImageMagick convert collides with windows 10 convert

Created on 23 Jan 2017  ·  6Comments  ·  Source: lukesampson/scoop

ImageMagick convert collides with windows 10 convert.

First time after installation it works ok. Then, after reboot PS takes windows exe instead of ImageMagick's one.
It is very annoying.
Please help!

Thanks

All 6 comments

I've added an imconvert alias to ImageMagick's convert, which should work even after rebooting.

The ImageMagick install is a little confusing because it adds the app directory to the PATH environment variable (which allows convert.exe to work temporarily) but then shims all the executables anyway. Ideally I think it would just add the shims, but maybe there's a reason for doing it that way that I don't understand.

But I digress. To get the imconvert command you will need to force a reinstall of ImageMagick, so scoop update; scoop uninstall imagemagick; scoop install imagemagick.

Thanks for the try, buddy.
Unfortunately it is not a real solution in case it is used by another application, such as in my case.
Rails uses ImageMagick's convert to process incoming images. I use it for test purpose so it is not so critical.

Let me know if you can figure out a way for ImageMagick's convert.exe to retain precedence after a reboot. It looks to me like Windows changes the order of your path environment variable on reboot to put C:\Windows\System32 before ~/scoop/shims and ~/scoop/apps/imagemagick/current.

Try creating an alias in your $PROFILE file for it. Something like

Set-Alias convert $(scoop which convert)

When you start PowerShell that should get run.

On Sat, 28 Jan 2017, 10:30 Luke Sampson notifications@github.com wrote:

Let me know if you can figure out a way for ImageMagick's convert.exe to
retain precedence after a reboot. It looks to me like Windows changes the
order of your path environment variable on reboot to put
C:\Windows\System32 before ~/scoop/shims and
~/scoop/apps/imagemagick/current.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lukesampson/scoop/issues/1253#issuecomment-275802618,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0QgmAaOmiaQb5WZYadDtueIDgF-7LGks5rWn4mgaJpZM4LqvGX
.

Let me know if you can figure out a way for ImageMagick's convert.exe to retain precedence after a reboot. It looks to me like Windows changes the order of your path environment variable on reboot to put C:\Windows\System32 before ~/scoop/shims and ~/scoop/apps/imagemagick/current.

@lukesampson you made me think and I was researching. After reading this article I reached the conclusion I had to install it globally. I rebooted my computer and tada!! it worked 👍

In summary:
scoop install sudo (In case you haven't got it already)
sudo scoop install imagemagick -g
Be happy 😃

@deevus I didn't try your suggestion but thanks anyway

I encountered the same problem when using Ruby minimagick's format function, which calls ImageMagick's convert in a shell in the background. The problem doesn't exist when you install ImageMagick with the normal installer, so it took me quite some time to pin this down to the scoop install of ImageMagick.

@zweimal 's workaround of installing ImageMagick globally worked, so thanks for that!

Should we maybe add that to the notes of ImageMagick?

A suggestion:

If your rely on the convert command of ImageMagick (like e.g. minimagick gem of Ruby) you have to install ImageMagick globally: (In a administrative shell) scoop install sudo + sudo scoop install imagemagick -g (Then restart the shell)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

eBaeza picture eBaeza  ·  3Comments

borekb picture borekb  ·  3Comments

vpratfr picture vpratfr  ·  3Comments

muhlpachr picture muhlpachr  ·  3Comments

ShivanshuKantPrasad picture ShivanshuKantPrasad  ·  3Comments