News for hackers. Stuff that matters.
Re:Show HN: A smarter Unix shell and scripting environment by still_grokking on Tuesday June 13, 2023 @05:55PM (#36318099)
> I think you're being a little unfair here

Maybe. But I just don't know why this discussion started in the first place. There is a `open` command on likely almost every desktop Linux box. So it's not Mac specific (which was my sole point in my first comment in this thread).

> Right, you said "alias" multiple times earlier. Symlinks and aliases are not the same thing.

You're technically correct. My fault!

I've called it alias as it's a symlink coming form the Debian alternatives facility. The alternatives mechanisms manages system wide command "aliases"… I should have been more exact in this point.

> I was saying I suspect Debian got the idea from macOS.

I have no prove but I doubt that. There were other tools on Linux called `open` before MacOS X came along as far as I know. The whole thing seems to be rooted in BSD (where NextStep got it's Unix parts form).

> For what it's worth "open" doesn't exist on my Ubuntu servers either.

Makes perfect sense. It's a desktop tool.

> And it was added to Debian only 2 years ago.

I don't think so. I had `xdg-utils` and it's `open` command installed for many years. It's at least 17 years old:

https://cgit.freedesktop.org/xdg/xdg-utils/refs/tags

> Anyway, this is all moot because there are easy workarounds for the naming conflict

I agree. The Debian alternatives system was made exactly to handle this kind of name conflicts around commands. So there's no big issue, indeed!

Re:Show HN: A smarter Unix shell and scripting environment by hnlmorg on Tuesday June 13, 2023 @06:03PM (#36318215)
`xdg-utils` has been around. But we're talking about the `open` symlink specifically. Here's the Debian 11 changelog: https://www.debian.org/releases/bullseye/amd64/release-notes...
Re:Show HN: A smarter Unix shell and scripting environment by still_grokking on Tuesday June 13, 2023 @06:11PM (#36318298)
Interesting!

I'm running Debian Testing so I had this command in fact since many years. Didn't know that it's actually quite "new".

Now I can understand how it could happen that Murex created a command name conflict. External tools don't test against Debian Testing most of the time…