3 ms·
I recently gave nushell a go for a few days, but I found that the structured data conveniences were not helpful all that often, at least compared to how often I
by n8henrie 3y ago
I recently gave nushell a go for a few days, but I found that the structured data conveniences were not helpful all that often, at least compared to how often I was having to look up redirecting stderr or similar bash incompatibilities.
The biggest workflow-breaking issue for me was the lack of task backgrounding. I am almost constantly working in vim, backgrounding to test out changes, fg to resume editing. Opening a new tmux / zellij pane instead did not work well (I work on a smallish screen, new pane doesn't have the old pane's command history).
- jiehong 3y agoFor background tasks, they recommend using pueue [0] with nushell. It feels like Powershell's Start-Job a bit. [0]: https://www.nushell.sh/book/background_task.html#using-nu-with-pueue https://www.nushell.sh/book/background_task.html#using-nu-wi...
- ctenb 3y agoThere is a learning curve and the standard library is not fully mature. Learning/reference resources are also not on par with bash, obviously. > new pane doesn't have the old pane's command history Sounds like a setup issue. You have to configure this manually for bash as well as nushell.
- n8henrie 3y agoI also have the problem in bash, as the history is not written until the shell exits (having it write history command-for-command results in interleaving history with commands from other sessions, which doesn't work well for me). But in bash, backgrounding works, so it's not an issue.