News for hackers. Stuff that matters.
Re:ImageMagick: CLI for Image Editing by coldpie on Wednesday December 01, 2021 @03:39PM (#29408857)
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
    imagemagick /usr/bin/stream
Re:ImageMagick: CLI for Image Editing by nauticacom on Wednesday December 01, 2021 @04:11PM (#29409194)
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
Re:ImageMagick: CLI for Image Editing by noobermin on Wednesday December 01, 2021 @06:54PM (#29410708)
tbf this sounds like a problem that doesn't need to be fixed... Ironically this would introduce problems where many scripts sort of assume the binaries have the names they have.
Re:ImageMagick: CLI for Image Editing by zamadatix on Wednesday December 01, 2021 @09:42PM (#29411892)
Scripts written for version 6 or older are probably going to have problems with version 8 or later anyways as that's what the major version number is there to represent.
Re:ImageMagick: CLI for Image Editing by alerighi on Wednesday December 01, 2021 @03:42PM (#29408884)
import is the most fun, when you forgot the `#!/usr/bin/env python` at the start of the script and of course the first instruction is import and you get an ImageMagik error
Re:ImageMagick: CLI for Image Editing by ReaLNero on Wednesday December 01, 2021 @03:44PM (#29408901)
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.
Re:ImageMagick: CLI for Image Editing by majkinetor on Wednesday December 01, 2021 @05:02PM (#29409712)
Sounds like you want PowerShell style naming :)
Re:ImageMagick: CLI for Image Editing by ReaLNero on Wednesday December 01, 2021 @06:51PM (#29410679)
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.

Re:ImageMagick: CLI for Image Editing by noobermin on Wednesday December 01, 2021 @06:55PM (#29410718)
This sentiment directly contradicts your post above...
Re:ImageMagick: CLI for Image Editing by ReaLNero on Thursday December 02, 2021 @01:54PM (#29420664)
I'm making a distinction between mnemonic names (du = disk usage) and just vague names (convert = ???).
Re:ImageMagick: CLI for Image Editing by enobrev on Wednesday December 01, 2021 @03:41PM (#29408877)
This is something I always preferred about the graphicsmagick fork, was the `gm` base command.
Re:ImageMagick: CLI for Image Editing by pxc on Wednesday December 01, 2021 @11:31PM (#29412583)
I came here to say the same thing
Re:ImageMagick: CLI for Image Editing by pavlov on Wednesday December 01, 2021 @05:42PM (#29410114)
No self-respecting Unix tool would use such long names, so that's why they were free. "compare" vs "cmp", etc.
Re:ImageMagick: CLI for Image Editing by Gigachad on Wednesday December 01, 2021 @06:01PM (#29410279)
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"
Re:ImageMagick: CLI for Image Editing by pavlov on Wednesday December 01, 2021 @07:40PM (#29411099)
I was trying to make a joke about the infamous naming practices of Unix, an operating system with a call named “creat”.
Re:ImageMagick: CLI for Image Editing by saghm on Wednesday December 01, 2021 @11:24PM (#29412551)
My favorite is "ioctl", which is especially delightful when pronounced phoenetically
Re:ImageMagick: CLI for Image Editing by noobermin on Wednesday December 01, 2021 @06:59PM (#29410760)
The reason the common commands were short was because typing on the keys for old terminals was a pain in general, and thus they are short for historical reasons. It is however an accident of history that them being shorter now makes it more convenient...if you have the names memorized.
Re:ImageMagick: CLI for Image Editing by ajkjk on Wednesday December 01, 2021 @07:16PM (#29410939)
A regrettable state that will hopefully be fixed someday.
Re:ImageMagick: CLI for Image Editing by contingencies on Wednesday December 01, 2021 @08:24PM (#29411403)
Spell create with an 'e'. - Ken Thompson (referring to design regrets on the UNIX creat(2) system call and the fallacy of premature optimization)

.. via https://github.com/globalcitizen/taoup

Re:ImageMagick: CLI for Image Editing by HeckFeck on Wednesday December 01, 2021 @04:34PM (#29409416)
If executable names were traded like internet domains, imagine what they'd be worth now.
Re:ImageMagick: CLI for Image Editing by technobabbler on Wednesday December 01, 2021 @05:18PM (#29409872)
I tried to convert those units but all I got was an imagemagick error
Re:ImageMagick: CLI for Image Editing by Meph504 on Wednesday December 01, 2021 @04:15PM (#29409227)
Image magick has been around for a pretty long time, and was doing image processing on linux before most had considered it.
Re:ImageMagick: CLI for Image Editing by Maursault on Wednesday December 01, 2021 @05:57PM (#29410246)
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.
Re:ImageMagick: CLI for Image Editing by pstuart on Wednesday December 01, 2021 @06:17PM (#29410393)
Your point would have been much better if you had stopped after the first sentence.
Re:ImageMagick: CLI for Image Editing by Meph504 on Thursday December 02, 2021 @11:26PM (#29426614)
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 by Maursault on Thursday December 09, 2021 @11:35AM (#29499493)
> 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 by Meph504 on Thursday December 09, 2021 @12:30PM (#29500306)
> 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.

Re:ImageMagick: CLI for Image Editing by Maursault on Friday December 10, 2021 @11:01AM (#29511423)
Thank you for explaining. I think I see now your observation is that ImageMagick was doing image processing on Linux before most had considered doing image processing on Linux. If so, then I am forced to concede this point. Although I think it is still fair to say, with a market share even now only barely breaching 2%, that most, in fact nearly all, have not considered doing anything at all on Linux since inception and likely not even five or ten years from now. This means those intrepid Linux+ImageMagick users processing images in the mid-1990's are that much more notable as those lucky few doing stuff with Linux before most had considered it, but also that those getting directory listings in Linux right this moment are also somewhat intrepid because most, maybe as much as 97.1%, had never considered even doing anything like that on Linux. I wonder what else most have not even considered doing on Linux. I expect nearly everything.
Re:ImageMagick: CLI for Image Editing by wnevets on Wednesday December 01, 2021 @03:50PM (#29408962)
the latest versions recommend that you use magick convert instead of just convert. I'm assuming because the globals are going away.
Re:ImageMagick: CLI for Image Editing by banana_giraffe on Wednesday December 01, 2021 @04:15PM (#29409230)
"convert" always gave me trouble on Windows with some existing tools that used Windows' built in "convert" tool. It was an edge case, but always entertaining when the tool needed to convert a filesystem or some tool I wrote wanted to convert an image, and got the wrong executable.
Re:ImageMagick: CLI for Image Editing by saghm on Wednesday December 01, 2021 @11:22PM (#29412537)
I totally agree and also had found it fascinating, except for...mogrify? I don't think I've ever heard that word before, and I don't even know what it could mean based on the only related word I can think of, "transmogrify".
Re:ImageMagick: CLI for Image Editing by herpderperator on Wednesday December 01, 2021 @04:40PM (#29409477)
This looks like useful output, what distro and command did you use to list this?
Re:ImageMagick: CLI for Image Editing by coldpie on Wednesday December 01, 2021 @05:15PM (#29409847)
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
Re:ImageMagick: CLI for Image Editing by 7kay on Wednesday December 01, 2021 @06:37PM (#29410560)
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/stream-im6.q16
Similarly, you get

     $ dpkg-query -S /usr/bin/convert-im6.q16 
     imagemagick-6.q16: /usr/bin/convert-im6.q16
This does not work for the canonical executables though as they are just symlinks to /etc/alternatives/foobar
Re:ImageMagick: CLI for Image Editing by pxc on Thursday December 02, 2021 @03:53AM (#29413924)
> 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 by rambojazz on Thursday December 02, 2021 @03:42AM (#29413854)
That's exactly my same thought every time I need to use one of those!
Re:ImageMagick: CLI for Image Editing by rdfi on Wednesday December 01, 2021 @06:25PM (#29410450)
Is there an easy way to get that list for a package?