Darren Schroeder
Darren Schroeder
What exactly is this trying to add? I'm not following. One can already use nushell as a default shell. I also have no idea what `lf` is.
if i understand your use case, your lf script is creating two scripts, foo and bar and all they have in them is the shebang. So, kind of just initializing...
I use MacOS every day and have never seen a hang like this. I wonder what's going on?
We don't like the config system much either. One thought was to break up the config in multiple parts/scripts but no one has been motivated enough to do that
I personally think it'll help to have the config in smaller chunks because each chunk could be parsed, then evaluated, then move on to the next file (like env.nu then...
I wonder why I can't reproduce it on Windows. 🤔  I tried both of these and got the same result. ```nushell ❯ which ssh -a ╭─#─┬command┬─────────────────path─────────────────┬───type───╮ │ 0 │...
I don't think it's my prompt. 
> erroneously identifies the input type based on the position of the command in the example pipeline would be nice to fix this somehow. any ideas?
The point is to be able to test the examples to ensure that what we're trying to explain is correct. We should absolutely be able to construct a pipeline ending...
I do this on macos and it works fine but I have vim aliased to nvim. ```nushell ls *.toml | vim ...($in.name) ```