Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ImageMagick: CLI for Image Editing

imagemagick.org

Post reply on HN
Print view View original

91–100 of 101 posts

Re: ImageMagick: CLI for Image Editing

#91

Post by pxc »

7kay wrote: post #64
coldpie wrote: post #52

Earlier quoted context omitted.

Arch Linux. $ pacman -Ql imagemagick | grep bin imagemagick /usr/bin/ imagemagick /usr/bin/Magick++-config imagemagick /usr/bin/MagickCore-config imagemagick /usr/bin/MagickWand-config imagemagick /usr/bin/animate imagemagick /usr/bin/compare .... You may also enjoy: $ pacman -Qo /usr/bin/{display,convert} /usr/bin/display is owned by imagemagick 7.1.0.16-1 /usr/bin/convert is owned by imagemagick 7.1.0.16-1

For reference (mostly for me as I need this from time to time), you can do the same on dpkg-based distros with $ dpkg -L imagemagick-6.q16 | grep bin /usr/bin /usr/bin/animate-im6.q16 /usr/bin/compare-im6.q16 /usr/bin/composite-im6.q16 /usr/bin/conjure-im6.q16 /usr/bin/convert-im6.q16 /usr/bin/display-im6.q16 /usr/bin/identify-im6.q16 /usr/bin/import-im6.q16 /usr/bin/mogrify-im6.q16 /usr/bin/montage-im6.q16 /usr/bin/…

> This does not work for the canonical executables though as they are just symlinks to /etc/alternatives/foobar

you can use realpath for this

  dpkg -S $(realpath /usr/bin/convert)
and you can ignore the path to it entirely with

  dpkg -S $(realpath $(which convert))

Re: ImageMagick: CLI for Image Editing

#92

Post by julik »

dkuder wrote: post #18

There are 634 CVE Records that match your search. https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=imagemagick There have been a number of zero days. My entire interaction with Imagemagick has been removing it. Often with great difficulty because there is some odd dependency.

I always find it remarkable how people bash on IM without proposing alternatives. Should we all write our own libpng, libtiff, skia, cairo? Even libvips uses some imagemagick facilities for some of its functionality (file format support is just not there). While yes, processing images is complex and some formats are nearly Turing-complete (or outright turing-complete like the container/MP4 derivatives) saying "This software contains vulnerabilities therefore we are going to remove it" is an attitude we could have less of. If you replace your local imagemagick with some cloud service - don't you worry, in addition to your cloud bill growing the cloud service _also_ has to deal with IM vulnerabilities, containerization, sandboxing and all the other good stuff. And is lilely saving money by not going all the way on the above (if I had a dollar for every time a vulnerability could be injected into a service where images can be uploaded and the image renderer starts going out to the internet to embed something into a PNG).

Re: ImageMagick: CLI for Image Editing

#93

Post by timonoko »

jackvalentine wrote: post #83
EamonnMR wrote: post #32

I did a project where I scanned a bunch of old media. The scans where so high quality that it was impractical to make a PDF for people to use. The Imagemagick community helped out with the right incantation to make everything just kinda work. One of the rare cases where a project's maintainers will just help you use it. I was wowed.

Was this on a public forum you can link?

I do book scanning a lot. Somebody might find these simple scripts useful: https://github.com/timonoko/BookScanner

Re: ImageMagick: CLI for Image Editing

#94

Post by undoware »

anthk wrote: post #81
undoware wrote: post #69

seeing ImageMagick, of all hoary tools, trending on HN reminds me that I'm so old that the kids are relishing as classics the tools I regard as outdated. This is expectable in music, but in tooling? And with Image -frigging- Magick ? Damn. Looking forward to the front-page HN-trended article on `sendmail`

The next ones will be mplayer, XFig, XPDF, nmh, TKGate for electronic boards, Links and Bochs. Back to 2002 again.

my default browser is.... [sunglasses emoji] Arena

Re: ImageMagick: CLI for Image Editing

#95

Post by ReaLNero »

noobermin wrote: post #68
ReaLNero wrote: post #66

Earlier quoted context omitted.

With good autocomplete, I wouldn't mind it! I was honestly thinking of stuff like `du` (disk usage), `cp`, `mv`, and the like. Like I sort of mnemonically remember them, compared to mentally mapping `convert` -> imagemagick.

This sentiment directly contradicts your post above...

I'm making a distinction between mnemonic names (du = disk usage) and just vague names (convert = ???).

Re: ImageMagick: CLI for Image Editing

#96

Post by anthk »

undoware wrote: post #94
anthk wrote: post #81

Earlier quoted context omitted.

The next ones will be mplayer, XFig, XPDF, nmh, TKGate for electronic boards, Links and Bochs. Back to 2002 again.

my default browser is.... [sunglasses emoji] Arena

Well, a lot of people use links -g and Netsurf daily :p.

HN works on texts, lots of blogs are plain text, and ofc you have http://68k.news, https://lite.cnn.io and https://text.npr.org.

Re: ImageMagick: CLI for Image Editing

#97

Post by EamonnMR »

jackvalentine wrote: post #83
EamonnMR wrote: post #32

I did a project where I scanned a bunch of old media. The scans where so high quality that it was impractical to make a PDF for people to use. The Imagemagick community helped out with the right incantation to make everything just kinda work. One of the rare cases where a project's maintainers will just help you use it. I was wowed.

Was this on a public forum you can link?

Discussion (with script) here: https://github.com/ImageMagick/ImageMagick/discussions/3124

The resulting PDFs are here: https://archive.org/details/@eamonnmr

Re: ImageMagick: CLI for Image Editing

#98

Post by Meph504 »

Maursault wrote: post #59
Meph504 wrote: post #30

Earlier quoted context omitted.

Image magick has been around for a pretty long time, and was doing image processing on linux before most had considered it.

ImageMagick was developed by John Cristy at DuPont in 1987 and release in 1990. Your statement is not only false, even it it wasn't, mentioning Linux in relation to ImageMagick is a non-sequitor. Maybe you should try other things.

Im really not sure what you are getting at?

I didn't say it was developed on/for Linux.

But because it was a mature product and added to Linux very early on, this is why it was able to get the names that it did.

so maybe you can share what it is you are responding to?

Re: ImageMagick: CLI for Image Editing

#99

Post by Maursault »

Meph504 wrote: post #98
Maursault wrote: post #59

Earlier quoted context omitted.

ImageMagick was developed by John Cristy at DuPont in 1987 and release in 1990. Your statement is not only false, even it it wasn't, mentioning Linux in relation to ImageMagick is a non-sequitor. Maybe you should try other things.

Im really not sure what you are getting at? I didn't say it was developed on/for Linux. But because it was a mature product and added to Linux very early on, this is why it was able to get the names that it did. so maybe you can share what it is you are responding to?

> Im really not sure what you are getting at?

To be quite clear, in the context of ImageMagick, claiming early Linux image processing with ImageMagick is irrelevant, also, not exactly true. What much does alleged Linux inclusion of any application (/usr/local/*) whatsoever have to do with that application? You're apparently promoting Linux by claiming it's a feat few had considered, or otherwise saying "I am cool," which is fine I guess and I don't doubt it, but also irrelevant.

As I pointed out, ImageMagick was developed in 1987, and I should have gone on to specify that most digital image manipulation techniques were developed in the 1960's. So assuming your Yggdrasil installation was processing images with it in early 1993, that it was "before most had considered it" is hardly knowable. I'm reading it similarly to saying your Chevy wipers were wiping your windshield before most had considered it when modern wipers were invented 50 years ago and all the techniques for doing so were worked out around the turn of the century. Chevy's are great and all, but there are other things.

Re: ImageMagick: CLI for Image Editing

#100

Post by Meph504 »

Maursault wrote: post #99
Meph504 wrote: post #98

Earlier quoted context omitted.

Im really not sure what you are getting at? I didn't say it was developed on/for Linux. But because it was a mature product and added to Linux very early on, this is why it was able to get the names that it did. so maybe you can share what it is you are responding to?

> Im really not sure what you are getting at? To be quite clear, in the context of ImageMagick, claiming early Linux image processing with ImageMagick is irrelevant, also, not exactly true. What much does alleged Linux inclusion of any application (/usr/local/*) whatsoever have to do with that application? You're apparently promoting Linux by claiming it's a feat few had considered, or otherwise saying "I am cool," w…

> claiming early Linux image processing with ImageMagick is irrelevant

It is at relevant, because this is about why imageMagick has such prime namespace on linux.

I don't have any idea why you are going in these seeming random directions, I'm not promoting linux, or whatever else your going on about.

This is my original statement

> Image magick has been around for a pretty long time, and was doing image processing on linux before most had considered it.

Surely we can both agree part below is a fair and accurate statement

> Image magick has been around for a pretty long time

This next part, is the part that seemingly needs clarification

> and was doing image processing on linux before most had considered it.

When imagemagick was added to linux in the mid 90s (near ImageMagick 4) not a lot of people were doing image processing in the OS. and being that it was the first mature image processor added to the distro, it is why it has the namespaces it does.

I'm not sure how you are either not getting that clarifier of "on linux" and seem to be trying to debate something about the history of image processing itself?

To be very clear, and to hopefully prevent this continued necro'ing of this post, I was not, talking about this history of image processing, but the specific linux namespace that imagemagick has, and why it has it.

Any other points of debate about this are irrelevant.

Post reply on HN