Posts tagged: bash

Reading eventbridge rules from the command line can be a total drag, pipe it into visidata to make it a breeze. I just love when I start thinking through how to parse a bunch of json at the command line, maybe building out my own custom cli, then the solution is as simple as piping it into visidata. Which is a fantastic tui application that had a ton of vim-like keybindings and data features. alias awsevents = aws events list-rules | visidata -f json

A super useful tool when doing PR’s or checking your own work during a big refactor is the silver searcher. Its a super fast command line based searching tool. You just run ag "<search term>" to search for your search term. This will list out every line of every file in any directory under your current working directory that contains a match. Ahead/Behind # [1] It’s often useful to need some extra context around the change. I recently reviewed a bunch of PR’s that moved schema from save_args to the root of the dataset in all yaml configs. To ensure they all made it to the top level DataSet configuraion, and not underneath save_args. I can do a search for all the schemas, and ensure that none of them are under save_args anymore. ag "schema: " -A 12 -B 12 References: [1]: #aheadbehind

Creating a minimal config specifically for git [1] commits has made running git commit much more pleasant. It starts up Much faster, and has all of the parts of my config that I use while making a git commit. The one thing that I often use is autocomplete, for things coming from elsewhere in the tmux session. For this cmpe-tmux specifically is super helpful. The other thing that is engrained into my muscle memory is jj for escape. For that I went agead and added my settings and keymap with no noticable performance hit. Here is the config that has taken ~/.config/nvim/init-git.vim source ~/.config/nvim/settings.vim source ~/.config/nvim/keymap.vim source ~/.config/nvim/git-plugins.vim lua require'waylonwalker.cmp' ~/.config/nvim/git-plugins.vim call plug#begin('~/.local/share/nvim/plugged') " cmp Plug 'hrsh7th/nvim-cmp' Plug 'hrsh7th/cmp-nvim-lsp' Plug 'hrsh7th/cmp-buffer' Plug 'hrsh7th/cmp-path' Plug 'hrsh7th/cmp-calc' Plug 'andersevenrud/compe-tmux', { 'branch': 'cmp' } call plug#end() ~/.gitconfig [core] editor = nvim -u ~/.config/nvim/init-git.vim References: [1]: /glossary/git/

I really appreciate that in linux anything can be scripted, including setting the wallpaper. So everytime I disconnect a monitor I can just rerun my script and fix my wallpaper without digging deep into the ui and fussing through a bunch of settings. feh --bg-scale ~/.config/awesome/wallpaper/my_wallpaper.png I set my default wallpaper with feh using the command above. Leaning in on feh, we can use fzf to pick a wallpaper from a directory full of wallpapers with very few keystrokes. alias wallpaper='ls ~/.config/awesome/wallpaper | fzf --preview="feh --bg-scale ~/.config/awesome/wallpaper/{}" | xargs -I {} feh --bg-scale ~/.config/awesome/wallpaper/{}' I have mine alias’d to wallpaper so that I can quickly run it from my terminal.

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...

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

I was completely stuck for awhile. copier was not replacing my template variables. I found out that adding all these _endops fixed it. Now It will support all of these types of variable wrappers # copier.yml _templates_suffix: .jinja _envops: block_end_string: "%}" block_start_string: "{%" comment_end_string: "#}" comment_start_string: "{#" keep_trailing_newline: true variable_end_string: "}}" variable_start_string: "{{" !RTFM: Later I read the docs and realized that copier defaults to using [[ and ]] for its templates unlike other tools like cookiecutter.

I’ve been looking for a templating tool for awhile that works well with single files. My go to templating tool cookiecutter does not work for single files, it needs to put files into a directory underneath of it. template variables # [1] By default copier uses double square brackets for its variables. variables in files, directory_names, or file_names will be substituted for their value once you render them. # hello-py/hello.py.tmpl print('hello-[[name]]') note! by default copier will not inject variables into your template-strings unless you use a .tmpl suffix. Before running copier we need to tell copier what variables to ask for, we do this with a copier.yml file. # copier.yml name: default: my_name type: str help: What is your name installing copier # [2] I prefer to install cli tools that I need globally with pipx, this always gives me access to the tool without worrying about dependency conflicts, bloating my system site-packages, or managing a separate virtual environment [3] for it myself. pipx install copier running copier # [4] When running copier copy we pass in the directory of the template, and the directory that we want to render the template into. cop...

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 ...