My current workflow is Windows or Linux in dual boot setting. I used WSL2 before in windows but stopped doing that and work native using Powershell.

I used the the dotfiles of Nic Nisi for a long time. You can still find some remnants of it. But seeing lots of Windots repos I decided to go native with powershell. Better for my machine learning loads.

I am using this Windots as base reference but I copy and paste from loads of others.

Goal is to go more and more in my own direction befitting my own workflows.

• Windows: ./Setup.ps1 all
• Linux: ./install.sh all

I have a docker container using a windows sandbox. Check the testing\windows folder.

There is also a docker container in testing\linux. For the moment you can just test the install script and the CLI. Not the gui aps like wezterm.

Yes I run powershell and not WSL2 on windows. I prefer to be native as this give me the max performance needed for my machine learning code. WSL always an out of memory crashing my jupyter kernels. Thanks to the work of Scott McKendry writing loads of powershell function to mimic, rm, grep, su, ... and loads more I feel like powershell is almost the same like my linux cli.

Not much explaining needed here... Look into the config.

Why starship and not a ZSH implementation? Well it runs everyhere. Powershell, ZSH and loads of other shells. Now I only need to maintain 1 configuration. But it is portable between OS'es.

Yes love this terminal and same reason. It is portable between OS'es.

• Want to add my windows configurations. I use tiling manager in windows and linux and want to sync their shortcuts.
• Add more specfic tweaks to the respective OS'es.
• There are loads of development environments I use and want them to de dployed automatically and on both OS'es.
• Cleanup and tidy up code - Ongoing
• Make the windows test environment work better
• Setup Gui test environment for linux to test my tiling manager configurations