Showcase of the windotfiles opening terminals, bottom and using update-winwal.
Warning
💀 Working in Windows is hard 💀
As you may know, at least for developers, Linux tends to be easier than Windows but Windows is the standard, at least for the videogames industry.
Tired of setting up Windows again and again on different machines or fresh installs I have decided to create a permanent way of keeping my changes and my setup.
On top of that, I'm decided to speed up my productivity with a window tilling manager similar to i3 on Linux 🌟 GlazeWM 🌟 and some other cool features and automatizations.
In this section we will describe all the necessary steps to install the windotfiles
Using the following command to clone the repository with PowerShell
cd $env:USERPROFILE
git clone --recurse-submodules https://github.com/Farravid/windotfiles.gitThis will clone the repository and also recursively clone the submodules.
Warning
If you don't clone the repository in the user's home directory, the setup won't work at all.
Most of the setup depends on this.
The main pre-requisite is to have the WinGet package manager operative. It should be available on the lastest Windows versions.
Nevertheless, and it is no surprise, WinGet could not work as expected with a fresh windows installation.
If you end up having the blue stuck problem visit this issue: microsoft/winget-cli#3832, specially the following code:
Invoke-WebRequest -Uri https://aka.ms/getwinget -OutFile winget.msixbundle
Add-AppPackage -ForceApplicationShutdown .\winget.msixbundle
del .\winget.msixbundle
This windotfiles repository uses Python and PowerShell for some of the functionalities.
We need to make sure those are installed on the system.
Warning
Python should be installed from winget, not from Microsoft Store. Make sure to use the same commands described here.
winget install Python.Python.3.13
winget install Microsoft.PowerShell
This should be enough to begin with the installation.
In order to fully install and use the windotfiles, you need to install some dependencies.
Some dependencies are mandatory for a basic windotfiles installation but others are optional since they are just preferences.
You can check the list of dependencies in the files scripts/common.
You will find it under REQUIRED and OPTIONAL WINGET_PROGRAMS
Go to the windotfiles folder and run the install.bat batch script as ADMIN
Warning
Windotfiles won't work if you don't run the script as admin
Warning
Adding the start-dotfiles task to the Task Scheduler is optional but recommended for faster inits.
Using the startup folder will be slower and less user friendly.
The windotfiles repository includes a start-dotfiles.xml that must be used to configure the Task Scheduler to start the dotfiles automatically on log on.
This task is in charge of launching the Startup launcher that will launch the setup.
After completing the previous steps, restart the system to fully apply the changes.
After the successful installation, you can still modify the windotfiles for your specific cases or use some of the functionalities described below.
This python script (startup.py) will be launched from the Task Scheduler every time you log in. It is in charge of launching GlazeWM and prompting the user with a setup selector.
Once the user has selected the setup and the default apps, that setup will be launched.
The default configuration is the basic configuration and but you can feel free of changing it in order to match your purposes and setups.
Note
Make sure to disable all the relevant programs from windows start up in order to have a perfect experience
In top of winwal, we have an update-winwal powershell command available for updating the color scheme based on the given wallpaper.
This command, for now, supports updating the color scheme of the following software:
Windows TerminalWezterm