Andrej Kolčin

Yeah, having it defined in the specification would be ideal. I think the main question is, should ``[`link`][]`` accept `[link]: ...` as a definition? Rust docs allow specifying a link...

I don't think it would. Windows has handles, but those are pointers and can't be created at will. So that'd have to be a Linux-only feature

Yeah, it's a Unix'ism. The main reason I'm asking for this is because this is a kind of thing can't be done by a third-party command, like `cd`. Plugins are...

@fdncred I think date to string conversion should use a machine readable format. And help can be whatever, really. I feel like `Value` needs `to_string()` and `to_human_string()` methods to separate...

Strings with spaces have to be quoted: `print "hello, world"`. A string can be executed using a caret: `^ls` (`ls` is a bare string in this example). So, paths with...

This would also require changing the semantics of unquoted strings, which do not support escapes. So, unlike in other shells, `print \t` will output `\t` literally.

If these terminals use bracketed paste mode, then it should be possible to catch these events and escape the whole path using Nushell-native quotes, much like the auto-completion does

Type inference might be tricky here, to the same degree that `extract` has to deal with. It'll probably require annotations somewhere. I personally prefer the let form: ```rust use pyo3::Unpackable;...

@fdncred I found it weird it was undocumented. Honestly, I don't get the utility of ranges in Nushell in general, since they can't be used for their primary use in...

Yeah, I forgot about the iteration, including `for`. I'd prefer a `range` function, but its just my minor bike shedding. I think adding the `x..y..z` to the docs is the...