Ever wanted to know how noice creates the cmdline or wanted your own one?
No one? Guess it's just me 🥲.
Anyway, this post is a simple tutorial for creating a basic cmdline in neovim.
| #!/bin/sh | |
| declare -r LINE_NUMBER_PANE_WIDTH=3 | |
| declare -r LINE_NUMBER_UPDATE_DELAY=0.1 | |
| declare -r COLOR_NUMBERS_RGB="101;112;161" | |
| declare -r COLOR_ACTIVE_NUMBER_RGB="255;158;100" | |
| open_line_number_split(){ | |
| local self_path=$(realpath $0) | |
| local pane_id=$(tmux display-message -pF "#{pane_id}") |
ASCI art characters for creating diagrams
This is a guide to configure React Native to be built for native and web platforms with Typescript, Vite.js and Storybook support for modelling components.
| #format = """ | |
| #[╭─user───❯](bold blue) $username | |
| #[┣─system─❯](bold yellow) $hostname | |
| #[┣─project❯](bold red) $directory$rust$git_branch$git_status$package$golang$terraform$docker_context$python$docker_context$nodejs | |
| #[╰─cmd────❯](bold green) | |
| #""" | |
| #format = '$all' | |
| [localip] | |
| ssh_only = false |
This is a brief guide on how to install Archlinux as a WSL2 distribution and how to set up CUDA afterwards.
As of late, Window's WSL2 offers GPU passthrough from WSL2/Linux to Windows for NVidia graphics cards which allows to run (and develop) CUDA-based applications on the WSL2/Linux-side with almost native performance. Unfortunately, the official guides for the CUDA setup for WSL2/Linux are predominantly Ubuntu-specific. Here's to you, Arch!
Archlinux is not among the default distributions available for WSL2. We'll install it from a tarball instead, a functionality offered natively by the WSL.
I'll spare everyone the rant. This gist will be an all business how to revert to WSL (Windows Subsystem for Linux) on Windows 10 from version 2 back to version 1.
Note that enabling Hyper-V destabilized the (highly managed) system my company provides me. This is probably unique to the image used for the machine and the updates that base has received. So I'm not surprised by the issues people are having with Hyper-V and the Virtual Machine Platform.
My personal Windows virtual machines remain on WSL 1 because I just don't have the energy to deal with all the drama when I've already put in a full shift at work.