3 ms·

(Sorry if too off-topic) I just saw this and thought this was pretty cool! Running your command in nushell, and eventually aborting it gives the following outp

(Sorry if too off-topic) I just saw this and thought this was pretty cool! Running your command in nushell, and eventually aborting it gives the following output ^CError: nu::shell::terminated_by_signal × External command was terminated by a signal ╭─[entry #28:1:32] 1 │ cat /dev/random | hexdump -C | grep 'ca fe' · ──┬─ · ╰── terminated by SIGINT (2) ╰──── Just wanted to random praise the nushell team for this amazing level of detail!

yencabulator 2y ago
Ehh. Nushell error handling is poorly built and buggy as hell. I wanted to use it, I really believed in the sales pitch, but it's just utterly unreliable and I have zero faith left in them ever actually fixing it. - error handling is neglected in the basic design: <https://github.com/nushell/nushell/issues/10633 https://github.com/nushell/nushell/issues/10633>, <https://github.com/nushell/nushell/issues/10856 https://github.com/nushell/nushell/issues/10856>, <https://github.com/nushell/nushell/issues/8615 https://github.com/nushell/nushell/issues/8615>, <https://github.com/nushell/nushell/issues/6617 https://github.com/nushell/nushell/issues/6617> - control-C interrupts its internals with obviously-wrong error: <https://github.com/nushell/nushell/issues/8828 https://github.com/nushell/nushell/issues/8828>, is midhandled in other ways <https://github.com/nushell/nushell/issues/8206 https://github.com/nushell/nushell/issues/8206> - something is horribly wrong with the basic design of command-line arguments: <https://github.com/nushell/nushell/issues/9939 https://github.com/nushell/nushell/issues/9939>, <https://github.com/nushell/nushell/issues/9766 https://github.com/nushell/nushell/issues/9766> - they're getting the fundamentals of globs on command lines wrong: if you pass string literals to an external command, they're still processed for globs. this means `ls ""` (internal) and `^ls ""` (external) behave differently: <https://github.com/nushell/nushell/issues/9558 https://github.com/nushell/nushell/issues/9558>

yencabulator 2y ago

Ehh. Nushell error handling is poorly built and buggy as hell. I wanted to use it, I really believed in the sales pitch, but it's just utterly unreliable and I have zero faith left in them ever actually fixing it. - error handling is neglected in the basic design: <https://github.com/nushell/nushell/issues/10633 https://github.com/nushell/nushell/issues/10633>, <https://github.com/nushell/nushell/issues/10856 https://github.com/nushell/nushell/issues/10856>, <https://github.com/nushell/nushell/issues/8615 https://github.com/nushell/nushell/issues/8615>, <https://github.com/nushell/nushell/issues/6617 https://github.com/nushell/nushell/issues/6617> - control-C interrupts its internals with obviously-wrong error: <https://github.com/nushell/nushell/issues/8828 https://github.com/nushell/nushell/issues/8828>, is midhandled in other ways <https://github.com/nushell/nushell/issues/8206 https://github.com/nushell/nushell/issues/8206> - something is horribly wrong with the basic design of command-line arguments: <https://github.com/nushell/nushell/issues/9939 https://github.com/nushell/nushell/issues/9939>, <https://github.com/nushell/nushell/issues/9766 https://github.com/nushell/nushell/issues/9766> - they're getting the fundamentals of globs on command lines wrong: if you pass string literals to an external command, they're still processed for globs. this means `ls ""` (internal) and `^ls ""` (external) behave differently: <https://github.com/nushell/nushell/issues/9558 https://github.com/nushell/nushell/issues/9558>