Adrian Valenzuela adrianvalenz

True Color (24-bit) and italics with alacritty + tmux + vim (neovim)

This should make True Color (24-bit) and italics work in your tmux session and vim/neovim when using Alacritty (and should be compatible with any other terminal emulator, including Kitty).

Testing colors

Running this script should look the same in tmux as without.

curl -s https://gist.githubusercontent.com/lifepillar/09a44b8cf0f9397465614e622979107f/raw/24-bit-color.sh >24-bit-color.sh

Credit

This is a frankensteind version of the current Soil nav walker, by the Roots team, and Michael Remoero's Sagextras walker. All credit goes to those good folks. :)

Use

Replace the contents of header.blade.php with the attached header.
Copy the walker.php file to the /app directory.
Add walker.php to the Sage required files array in resources/functions.php - eg. on a stock Sage install the entry would look like:

/**

MySQL

Getting started

Branching

Quick Legend

Description, Instructions, Notes

Instance	Branch

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

	foreground #d8cacc
	background #323d43
	selection_foreground #3c474d
	selection_background #525c62
	url_color #415c6d
	cursor #7fbbb3

	# black
	color0 #4a555b
	color8 #525c62

	<%# Put this code snippet between the <head></head>-tags in your application layout and %>
	<%# replace 'UA-XXXXXXXX-X' with your own unique Google Analytics Tracking ID %>

	<%# ... %>
	<head>
	<%# ... %>
	<% if Rails.env.production? %>
	<script type="text/javascript">
	(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]\|\|function(){
	(i[r].q=i[r].q\|\|[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),

	AllCops:
	RunRailsCops: true

	# Commonly used screens these days easily fit more than 80 characters.
	Metrics/LineLength:
	Max: 120

	# Too short methods lead to extraction of single-use methods, which can make
	# the code easier to read (by naming things), but can also clutter the class
	Metrics/MethodLength:

	If you are running a large website where you will need to test new features on a seperate url before pushing them live then the following instructions are for you ;)

	For this example imagine your url is apple.com and you want a development/staging site on a subdomain which is dev.apple.com

	#Setup#
	1. First thing you'll want to do is go ahead and create your website in plesk and add the subdomain dev.apple.com at the same time.
	2. ssh into the server e.g. $ ssh username@ipaddress
	3. Once logged in cd into the private directory (this will be where all git repos are stored) e.g. $ cd ~/private
	4. Create the main repo e.g. $ git init --bare apple.git
	5. Now to clone this new repo on your local machine. $ git clone ssh://username@ipaddres/~/private/apple.com