I have created an interactive installation script, that is probably only useful for myself during setting up a new Linux environment. An easy way of setting up my dotfile system is to use curl or wget to fetch the install script and execute it. Warning: selecting 'replace' will overwrite old files, see below for more information.
bash <(curl -sL sampo.website/install-dotfiles.sh)Or using wget
bash <(wget -qO - sampo.website/install-dotfiles.sh)If you select 'clone', it just clones this repository. With 'replace' it creates a bare git repository in ~/.dotfiles/ and clones this repository there and checkout all the files in this repository into the home directory of the user. This will overwrite all previous files with same paths than in repository. Make sure to backup beforehand as there is no undo or automatic backups, or just clone the repository and do copying manually.
- The "
curl -sL https://url/script.sh | bash" way does not currently work with the install script as it's interactive. However,bash -c "$(curl -sL sampo.website/install-dotfiles.sh)"will work. - The actual file location is https://raw.githubusercontent.com/samporapeli/dotfiles/main/Documents/install-dotfiles.sh and sampo.website has a redirect to that location.
This might be a good idea if you only want some parts of the configuration.
- Clone this repository, e. g.
git clone https://github.com/samporapeli/dotfiles.git - In repository directory, load git submodules:
git submodule init && git submodule update - Copy/link files from repository to needed locations in home directory.
There's a small list of document editing related packages at [~/Documents/document-packages.apt.txt] including a full texlive install for creating documents using Latex. This is not included in the base install, as the size of the installation is rather big. Install packages from file:
sudo apt install $(tr '\n' ' ' < ~/Documents/document-packages.apt.txt)TODO: add helper function for this and use it here and in install script.
My vim plugin ecosystem configuration is a bit spaghetti, so I'm writing down the required steps for making the nide alias work as it should.
WIP Setting up:
- Install
npm - Make sure that the
$HOME/.config/nvim/contains files from this repository, e.g., rundot pull. vim-plugin update, however might not be necessarynide -c PackerUpdate
Vim 8 introduced native package management, and that is what I use. Here you can find a good tutorial on how to set it up with git submodule. I currently use the path ~/.vim/pack/sampo/start for all plugins.
However, I created a small tool that automates some steps during adding, deleting and updating plugins. It is located in ~/bin/vim-plugin. Should I just use some actual vim plugin manager? Probably, but I couldn't resist writing this.
Basic usage (with example plugin):
# Add a new plugin
vim-plugin add https://github.com/vim-airline/vim-airline.git
# Update all installed plugins and generate helptags
vim-plugin update
# Delete a plugin
vim-plugin delete vim-airlineInstall or update nvm: install-nvm
As loading nvm in .zshrc increases shell startup time, I decided to load nvm manually when needed: . load-nvm (or source load-nvm)
This is the place for most of my custom scripts. Some are so simple that they could as well be aliases, while some are a bit more complicated. This is added to $PATH, so it is super easy to create new executables.
Some useful functions that can be used in other scripts.
Plasma + bspwm
Plasma but bspwm instead of kwin. picom as a compositor.
This repository contains some configuration files related to my second computer running Arch Linux and i3wm.
There is Windows specific configuration in .windows-config directory, currently only configuration file for Windows Terminal.
Configuration files to make programs work in certain (read: right 😁) way, like .latexmkrc to use PDF as default format.