Posts tagged: linux

Stow is an incredible way to manage your dotfiles. It works by managing symlinks between your dotfiles directory and the rest of the system. You can then make your dotfiles directory a git [1] repo and have it version controlled. In my honest opinion, when I was trying to get started the docs straight into deep detail of things I frankly don’t really care about and jumped right over how to use it. When using stow its easiest to keep your dotfiles directory (you may name it what you want) in your home directory, with application directories inside of it. Then each application directory should reflet the same diretory structure as you want in your home directory. zsh # [2] Here is a simple example with my zshrc. mkdir ~/dotfiles cd ~/dotfiles mkdir zsh mv ~/.zshrc zsh stow --simulate zsh You can pass in the –simulate if you wish, it will tell you if there are going to be any more errors or not, but it wont give much more than that. WARNING: in simulation mode so not modifying filesystem. Once your ready you can stow your zsh application. stow zsh nvim # [3] A slightly more complicated example is neovim since its diretory structure does not put configuration files directl...

The copier answers file is a key component to making your templates re-runnable. Let’s look at the example for my setup.py. ❯ tree ~/.copier-templates/setup.py /home/walkers/.copier-templates/setup.py ├── [[ _copier_conf.answers_file ]].tmpl ├── copier.yml ├── setup.cfg └── setup.py.tmpl 0 directories, 4 files Inside of my [[ _copier_conf.answers_file ]].tmpl file is this, a message not to muck around with it, and the ansers in yaml form. The first line is just a helper for the blog post. # ~/.copier-templates/setup.py/\[\[\ _copier_conf.answers_file\ \]\].tmpl # Changes here will be overwritten by Copier; NEVER EDIT MANUALLY [[_copier_answers|to_nice_yaml]] Inside my copier.yml I have setup my _answers_file to point to a special file. This is because this is not a whole projet template, but one just for a single file. # copier.yml # ... _answers_file: .setup-py-copier-answers.yml Once I change the _answers_file I was incredibly stuck Run it # [1] I’m making a library of personal copier templates in my ~/.copier-templates directory and I am going to run it from there. copier copy ~/.copier-templates/setup.py Results # [2] After rendering the template we have the followi...

I’ve been stuck many times looking at a vim buffer with little question marks at the beginning of each line and trying to get rid of them. for so long I didn’t know what they were so trying to get rid of them was impossible. [1] It turns out they are tabs, and you can get rid of the little leading question marks with this substitution command. :%s/\t/ /g References: [1]: https://images.waylonwalker.com/vim-tab-characters.png

tmux popups can be sized how you like based on the % width of the terminal on creation by using the flags (h, w, x, y) for height, width, and position. # normal popup tmux popup figlet "Hello" # fullscreen popup tmux popup -h 100% -w 100% figlet "Hello" # 75% centered popup tmux popup -h 100% -w 75% figlet "Hello" # 75% popup on left side tmux popup -h 100% -w 75% -x 0% figlet "Hello" Sorry, your browser doesn't support embedded videos. example running these commands

One of the most useful skills you can acquire to make you faster at almost any job that uses a computer is getting good at finding text in your current working diretory and identifying the files that its in. I often use the silver searcher ag or ripgrep rg to find files in large directories quickly. Both have a sane set of defaults that ignore hidden and gitignored files, but getting them to list only the filenames and not the matched was not trivial to me. I’ve searched throught he help/man pages many times looking for these flags and they always seem to evade me. ag # [1] Passing the flag -l to ag will get it to list only the filepath, and not the match. Here I gave it a --md as well to only return markdown filetypes. ag supports a number of filetypes in a very similar way. ag nvim --md -l rg # [2] Giving rg the --files-with-matches flag will yield you a similar set of results, giving only the filepaths themselves and not the match statement. Also passing in the -g "*.md" will similarly yield only results from markdown files. rg --files-with-matches you -g "*.md" References: [1]: #ag [2]: #rg

pyenv provides an easy way to install almost any version of python from a large list of distributions. I have simply been using the version of python from the os package manager for awhile, but recently I bumped my home system to Ubuntu 21.10 impish, and it is only 3.9+ while the libraries I needed were only compatable with up to 3.8. I needed to install an older version of python on ubuntu I’ve been wanting to check out pyenv for awhile now, but without a burning need to do so. installing # [1] Based on the Readme it looked like I needed to install using homebrew,so this is what I did, but I later realized that there is a pyenv-installer repo that may have saved me this need. Installing Homebrew on Linux [2] List out install candidates # [3] You can list all of the available versions to install with pyenv install --list. It does reccomend updating pyenv if you suspect that it is missing one. At the time of writing this comes out to 532 different versions! pyenv install --list Let’s install the latest 3.8 patch # [4] Installing a version is as easy as pyenv install 3.8.12. This will install it, but not make it active anywhere. pyenv install 3.8.12 let’s use python 3.8...

Installing brew on linux proved quite easy and got pyenv running for me within 4 commands. I had never used homebrew before, honestly I thought it was a mac only thing for years. Today I wanted to try out pyenv, and the reccommended way to install was using homebrew. I am not yet sure if I want either in my normal workflow, so for now I am just going to pop open a new terminal and install homebrew and see how it goes. /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" echo 'eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"' >> /home/walkers/.zprofile eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)" That was it, now homebrew is working. Starting a new shell and running the command to install pyenv worked. brew install pyenv Links # [1] - homebrew [2] References: [1]: #links [2]: https://brew.sh/

When I first moved to vim from and ide like vscode or sublime text one of my very first issues was trying to preview my website at localhost:8000. There had always just been a button there to do it in all of my other editors, not vim. There are not many buttons for anything in vim. While there is probably a plugin that can run a webserver for me in vim, it’s not necessary, we just need the command line we are already in. running a separate process # [1] You will need a way to run another process alongside vim, here are a couple ideas to get you going that are not the focus here.style - use background jobs - c-z to send a job to the background - fg to bring it back - use a second terminal - use a second tab - use tmux and run it in a separate split/window - use an embeded nvim terminal running a development webserver from the command line # [2] Python already exists on most linux systems by default, and most are now on python3. If you are on windows typing python will take you directly to the windows store to install it, or you can also use wsl. # python3 python -m http.server # running on port 5000 python -m http.server --directory markout 5000 # for the low chance ...