iTranslated by AI
Building the Fastest Windows Terminal Environment with Nushell + Starship (2022)
Support for Ver0.60.0
Related Article:
Building the fastest Windows terminal environment with Nushell + Starship
------------------- ↓ The main topic starts here ↓-------------------
It has been several years since I started using Nushell + StarShip.
I had memorized the commands and was using them comfortably, but then something shocking happened.
The arrival of Ver. 0.60.0
I am not sure if they rebuilt it from scratch, but the internals have changed completely.
I don't think it will work if you follow the installation steps from my previous article (I haven't tested it). So, this time, I decided to build the environment for the new version.
ヾ(・ω<)ノ" 三三三● ⅱⅲ Rolling along♪
------------------- ↓ The main topic starts here ↓-------------------
Installing winget
The installation of Nushell itself hasn't changed much.
This assumes your Windows 10 is up to date.
Install the App Installer from the Microsoft Store.
Installing Nushell
Install via winget.
Close PowerShell once to adjust the PATH.
I will also install gsudo since I need administrative privileges.
winget install gsudo
gsudo winget install Nushell.Nushell
exit
Launching Nushell
Restart PowerShell and launch Nushell.
On the first launch, it will ask if you want to create a configuration file; select y.
nu --version
0.60.0
nu

(・o・) Maybe it became more colorful?
Exit back to PowerShell for now.
exit
Installing StarShip
Since StarShip is now registered in winget, I will install it via that.
winget install Starship.Starship
Restart the terminal to apply the PATH settings. Restart PowerShell, then launch Nushell to verify the path.
nu
starship --version
03/26/2022 10:28:11 PM
starship 1.5.4
tag:v1.5.4
commit_hash:d420a63e
build_time:2022-03-24 19:26:50 +00:00
build_env:rustc 1.59.0 (9d1b2106e 2022-02-23),stable-x86_64-pc-windows-msvc
Configuring StarShip
Set it up so StarShip launches when Nushell starts.
Previously, it felt like setting a startup prompt, but this time it seems the flow is to write it into the configuration file.
mkdir ~/.cache/starship/
starship init nu | save ~/.cache/starship/init.nu
echo "source ~/.cache/starship/init.nu\n"| save --append ($nu.config-path)
Restart NuShell.

(・∀・) Fixed!
------------------- ↓ Postscript starts here ↓-------------------
For now, it seems like I can continue using it even with the new version.
Although all the commands I had memorized so far have been discarded, I guess I will just take my time learning them again.
I have written about installing fonts and Linux-style commands in my previous article, so please take a look at that as well.
Discussion