Interesting. Looks similar to nushell [1] which also is data-encoding-aware.

▲ xalava 5 days ago | parent [-]

Thanks for pointing it out. I've tried both as interactive shells for a few minutes. Murex seems to have a more minimalist approach that works well as a drop-in replacement.

However, I have trouble understanding some design decision, such as inventing redundant keywords. And I've spotted bugs in boths (e.g. ls --literal fails in nu, and the completion proposes it twice in Murex).

▲ MyOutfitIsVague 4 days ago | parent | next [-]

`ls` is not the same command in nu. There's a nu-specific `ls`.

My GNU `ls` has `--literal`, but to do that in nu, you have to do `^ls --literal`, to use the external command instead of the nu builtin.

You can see the nu `ls` options with `help ls`, or `ls --help`. `--literal` is completely useless for nu's `ls` anyway. `nu`'s ls gives a table, where the `name` column is the filenames. There's no need for any quoting, because it's already structured output.

▲ hnlmorg 3 days ago | parent | prev | next [-]

> However, I have trouble understanding some design decision, such as inventing redundant keywords.

Murex author here: The design was originally based around explicitness. Though that's not to say that the design works everywhere. So I'm definitely interested to understand where you think improvements can be made. Please do leave some feedback in Github.

▲ esafak 4 days ago | parent | prev [-]

ls --literal does not exist, that's why. Try man.

▲ arp242 4 days ago | parent [-]

       -N, --literal
              print entry names without quoting

	▲	OJFord 3 days ago \| parent [-]
		Is that from nu ls' help/man page?