61–70 of 101 posts
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.
At my $OLDJOB, I used ImageMagick to compare snapshots during some automated front-end testing on our public Drupal site. It would compare the running test to previously accepted images, highlighting pixel diffs in red. It would also generate a 4 frame animated gif with of the original, highlit changes, the running test version, and back to the highlit changes (so it could loop for better comparison). Imagemagick sav…
Thanks for sharing this tip! Are there any guides you recommend? Edit: Here’s one guide for the legacy Imagemagick (may not work for the latest release), https://legacy.imagemagick.org/Usage/compare/ I’m trying to encourage my front end developers to use visual diffs to validate rendering rather than use Protractor to test HTML/CSS. I’ve known about BackstopJS, https://garris.github.io/BackstopJS/ and am on the looko…
I always found it fascinating the grade-A executable names which imagemagick was able to claim in the global namespace: imagemagick /usr/bin/animate imagemagick /usr/bin/compare imagemagick /usr/bin/composite imagemagick /usr/bin/conjure imagemagick /usr/bin/convert imagemagick /usr/bin/display imagemagick /usr/bin/identify imagemagick /usr/bin/import imagemagick /usr/bin/mogrify imagemagick /usr/bin/montage imagemag…
Earlier quoted context omitted.
This looks like useful output, what distro and command did you use to list this?
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
$ 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/stream-im6.q16
$ dpkg-query -S /usr/bin/convert-im6.q16
imagemagick-6.q16: /usr/bin/convert-im6.q16
Earlier quoted context omitted.
They are pretty common verbs, but they give 0 context to the user on what they do. I don't think these names are in any demand -- there's always a better name than "import" for your command line utility.
Sounds like you want PowerShell style naming :)
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.
I always found it fascinating the grade-A executable names which imagemagick was able to claim in the global namespace: imagemagick /usr/bin/animate imagemagick /usr/bin/compare imagemagick /usr/bin/composite imagemagick /usr/bin/conjure imagemagick /usr/bin/convert imagemagick /usr/bin/display imagemagick /usr/bin/identify imagemagick /usr/bin/import imagemagick /usr/bin/mogrify imagemagick /usr/bin/montage imagemag…
Thankfully as of v7 these are all bundled under a single "magick" command (with symlinks for compatibility). Hopefully in the future these can be removed
Earlier quoted context omitted.
Sounds like you want PowerShell style naming :)
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 is expectable in music, but in tooling?
And with Image-frigging-Magick ?
Damn.
Looking forward to the front-page HN-trended article on `sendmail`
Earlier quoted context omitted.
No self-respecting Unix tool would use such long names, so that's why they were free. "compare" vs "cmp", etc.
Image magick isn't something you use frequently and quickly like changing directories or moving a file. A longer more descriptive name is better here. Also easier to speak. Telling someone to write "compare" is easier than "C-M-P"