# nushell Published articles for nushell. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Nushell, after 8 months DevFeed: [Nushell, after 8 months]() Original publisher: [Read original article]() Author: Manideep Polireddi Published: 2024-04-29T11:15:00Z Content type: article Language: en Sources: [@okmanideep]() Topics: [Shell](), [Command-line interface](), [Programming](), [data]() Tags: [bash](), [cli](), [csv](), [json](), [nushell](), [powershell](), [shell](), [sqlite](), [yaml](), [zsh]() ### AI overview The author reflects on using Nushell as their primary shell for eight months. They find its table-based structured data model useful for CLI work, data wrangling, Kubernetes commands, and processing formats such as CSV, JSON, YAML, TOML, and SQLite, while reporting few problems interoperating with Unix programs that expect plain text. ### Source excerpt I have been using nushell as my primary shell for the last 8 months and I don't see myself going back to bash or zsh or powershell ## I am very excited about using nushell everyday DevFeed: [I am very excited about using nushell everyday]() Original publisher: [Read original article]() Author: Manideep Polireddi Published: 2023-08-28T13:00:00Z Content type: opinion Language: en Sources: [@okmanideep]() Topics: [Structured-data](), [Bash](), [PowerShell](), [Command-line interface](), [Terminal](), [Scripting]() Tags: [bash](), [here](), [nushell](), [optimizing](), [plugins](), [powershell](), [terminal]() ### AI overview The author explains why Nushell appeals to them as a structured-data shell combining aspects of Bash and PowerShell. They compare Nushell's table-oriented pipelines and clearer property-based sorting with Unix-style commands, while noting that startup and new-terminal performance remain slow despite profiling and optimization. ### Source excerpt From the moment I saw the intro video, I found it very appealing. It takes the best of bash and powershell ## Maybe I can Stay in NuShell -or- Living in a Diverse Land of Shells DevFeed: [Maybe I can Stay in NuShell -or- Living in a Diverse Land of Shells]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-07-20T09:36:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Shell](), [Command-line interface](), [Bash](), [Zsh]() Tags: [bash](), [command](), [nushell](), [rails](), [ruby](), [rvm](), [shell](), [zsh]() ### AI overview The author explains that they can continue using NuShell as their main shell while switching to Bash or Zsh when tools such as RVM require them. A Rails project is successfully created after switching to Bash. ### Source excerpt I really, really like NuShell. The realization that maybe I had to leave was, I'll admit, mildly crushing. And then I just had the realization that maybe I don't have to leave NuShell and slink back to the dirty, byte infested corners of Bash and Zsh. Here's what just happened: /Users/sjohnson/Sync/coding/flow_analytics/open_source〉rails new pool_api --api Rails is not currently installed on this system. To get the latest version, simply type: $ sudo gem install rails You can then rerun your "rails" command. /Users/sjohnson/Sync/coding/flow_analytics/open_source〉ruby -v 07/20/2022 05:34:41 AM ruby 2.6.8p205 (2021-07-07 revision 67951) [universal.x86_64-darwin21] /Users/sjohnson/Sync/coding/flow_analytics/open_source〉rvm use And that was the point when I realized "Oh yeah - RVM doesn't work on NuShell" and then it struck me - I can run Bash: /Users/sjohnson/Sync/coding/flow_analytics/open_source〉/bin/bash 07/20/2022 05:34:57 AM bash: /Users/sjohnson/Library/Python/2.7/bin/powerline-config: /usr/bin/python: bad interpreter: No such file or directory bash: /Users/sjohnson/Library/Python/2.7/bin/powerline-config: /usr/bin/python: bad interpreter: No such file or directory bash: /Users/sjohnson/.iterm2_shell_integration.nu: No such file or directory ERROR: Can't find Ruby library file or shared library lunchy usage: dirname string [...] The default interactive shell is now zsh. To update your account to use zsh, please run `chsh -s /bin/zsh`. For more details, please visit https://support.apple.com/kb/HT208050. [sjohnson:~/Sync/coding/flow_analytics/open_source] [base] $ rails new pool_api --api create create README.md create Rakefile create .ruby-version create config.ru create .gitignore create .gitattributes create Gemfile run git init from "." ... So maybe my system can mostly run NuShell and I can drop in and out of Bash / Zsh when I need different things. Fingers Crossed. ## Getting NuShell Usable Under OSX for Myself DevFeed: [Getting NuShell Usable Under OSX for Myself]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-07-17T15:20:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Shell](), [osx](), [Command-line interface](), [Homebrew](), [Terminal](), [configuration](), [chmod]() Tags: [bash](), [blog-post](), [chmod](), [coding](), [commands](), [config](), [how-to](), [install](), [nushell](), [osx](), [rust](), [shell](), [terminal]() ### AI overview A practical guide to making NuShell usable as a daily shell on OSX Monterey. It covers changing the default shell, preserving Bash history, fixing Homebrew path access, configuring persistent environment settings, and defining aliases. ### Source excerpt Pizza courtesy of Pizza for Ukraine! Donate Now to Pizza for Ukraine As I've written, I'm acutely interested in using software written in Rust as my daily drivers. What I've seen so far is that programs written in Rust, based on an admittedly tiny sample, seem to be higher quality than programs not written in Rust. In this blog post, I'm going to talk about what I had to do to make NuShell be usable for myself under OSX Monterey. To be perfectly honest, I don't know if my experiences are normal or not. I seem to have a high personal level of entropy with respect to software and it appears that at least sometimes this level of entropy causes bugs. This is the main reason that I document things so dogmatically - I often need to refer to my own blog. Step 00: Changing Your Shell to NuShell After you install NuShell, you are left a bit on your own. You can invoke it via the nu command but what you really want is it to come up as the default shell. This is done with chsh: sudo chsh -s /usr/local/bin/nu sjohnson NOTE: DO NOT CLOSE ALL YOUR OLD TERMINALS!!! If you are like me and are heavily reliant on history then you want to do this in an existing Bash / Zshell / Fish / Whatever terminal window: history > ~/history_old.txt chmod +r ~/history_old.txt Yes - I think that strongly about history that I want this read only so it doesn't get killed inadvertently. Step 01: Getting Brew to Function After you switch over to using NuShell, you may find that programs like brew aren't found. This is a path issue (isn't everything???). Here's an example: /Users/sjohnson/Sync/coding/flow_analytics〉brew 07/17/2022 10:59:12 AM Error: nu::shell::external_command (link) x External command ╭─[entry #11:1:1] 1 │ brew - ──┬─ - ╰── can't run executable ╰──── help: No such file or directory (os error 2) The solution is to add brew's path into the NuShell environment. Back in your old shell window, type: Sync/coding/flow_analytics on ☁ (us-west-2) ❯ which brew /usr/local/bin/brew This tells us ## NuShell - When /bin/bash curl installs fail DevFeed: [NuShell - When /bin/bash curl installs fail]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-07-09T02:57:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Scripting, bash](), [Bash](), [cURL](), [Homebrew](), [Perl]() Tags: [bash](), [curl](), [homebrew](), [nushell](), [perl](), [rust](), [script]() ### AI overview The author reports that several commands and scripts failed when run directly in NuShell, including Homebrew install and uninstall commands. The suggested workaround is to start a /bin/bash session from NuShell, run the needed commands there, and type exit to return to NuShell. ### Source excerpt I've liked the concept of NuShell since I first heard about it. I then liked it more when I discovered that Yehuda Katz was involved since I strongly believe in picking software based on the pedigree of the engineers involved (no I don't - yet - have engineer trading cards but I'm thinking about it). Although I have NuShell running on my experimental system, I've held off on using it on my main box mostly due to concerns about the vast amounts of things that pipe crap to /bin/bash like this: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/uninstall.sh)" /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" /usr/bin/find "$(brew --prefix)/Caskroom/"*'/.metadata' -type f -name '*.rb' -print0 | /usr/bin/xargs -0 /usr/bin/perl -i -0pe 's/depends_on macos: \[.*?\]//gsm;s/depends_on macos: .*//g' That's an uninstall script, an install script and a find command. I tried all of these tonight on NuShell and they all failed. An example of this is: /Users/sjohnson/Sync/coding〉/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" /bin/bash: #!/bin/bash: No such file or directory /Users/sjohnson/Sync/coding〉 Note: For non NuShell users, you can tell its NuShell above by the greater than sign in the prompt. And then it struck me - I can likely simply execute /bin/bash from within NuShell and THEN run whatever I need to in bash. I tried it and it worked perfectly. So if you have problems with things that don't work on NuShell, try spinning up a /bin/bash session. After you're done, type exit and you are back in NuShell.