Antoine Cotten antoineco

Redirect the output of a Vim or external command into a scratch buffer

Usage (any shell)

Show the full output of command :hi in a scratch buffer:

:Redir hi

Show the full output of command :!ls -al in a scratch buffer:

The right way to override any highlighting if you don't want to edit the colorscheme file directly

Generalities first

Suppose you have weird taste and you absolutely want:

your visual selection to always have a green background and black foreground,
your active statusline to always have a white background and red foreground,
your very own deep blue background.

My Vim-related gists

Long-form

HTML Tags You Can Use on GitHub

Wherever HTML is rendered on GitHub (gists, README files in repos, comments on issues and pull requests, ...) you can use any of the HTML elements that GitHub Flavored Markdown (GFM) provides syntactic sugar for. You can either use the syntactic sugar that GFM (or other GitHub-supported markup language you're using) provides or, since Markdown can contain raw HTML, you can enter the HTML tags manually.

But GitHub also allows you to use a few HTML elements beyond what Markdown provides by entering the tags manually, and some of them are styled with CSS. Most raw HTML tags get stripped before rendering the HTML. Those tags that can be generated by GFM syntactic sugar, plus a few more, are whitelisted. These aren't documented anywhere that I can find. Here's what I've discovered so far:

`<details>` and `<summary>`

A `<detai

Seamlessly editing remote files in (Neo)Vim with Netrw and scp

Neovim and Vim both come bundled with a standard plugin called Netrw. Netrw acts a file explorer (similar to NERDTree), but more importantly has the ability to work with scp (as well as sftp, rcp, ftp, and lots of others :h netrw-nread) to let you edit files and browse directories that are hosted on a remote machine, inside of your local Vim instance.

This is useful since you are able to use your Vim setup and plugins without copying over your dotfiles to the remote machine. As well, since the file is copied to your local machine, there will be no delay when typing.

Setup

This is optional for Vim, but required for Neovim (check this Neovim issue explaining why).

	##############
	# pretty prompt and font colors
	##############

	# alter the default colors to make them a bit prettier
	echo -en "\e]P0000000" #black
	echo -en "\e]P1D75F5F" #darkred
	echo -en "\e]P287AF5F" #darkgreen
	echo -en "\e]P3D7AF87" #brown
	echo -en "\e]P48787AF" #darkblue

	#!/boot/bzImage

	# Linux kernel userspace initialization code, translated to bash
	# (Minus floppy disk handling, because seriously, it's 2017.)
	# Not 100% accurate, but gives you a good idea of how kernel init works
	# GPLv2, Copyright 2017 Hector Martin <[email protected]>
	# Based on Linux 4.10-rc2.

	# Note: pretend chroot is a builtin and affects the current process
	# Note: kernel actually uses major/minor device numbers instead of device name

	az vmss extension set \
	--vmss-name <vmss-name> \
	-g <resource-group> \
	-n VMAccessForLinux \
	--publisher Microsoft.OSTCExtensions \
	--version 1.4 \
	--protected-settings "{\"username\":\"deploy_user\", \"ssh_key\":\"$(cat ~/.ssh/id_rsa.pub)\"}"
	# Upgrade ALL instances in the scale set with the new key
	az vmss update-instances --instance-ids '*'
	-n <vmss-name>

	apiVersion: extensions/v1beta1
	kind: PodSecurityPolicy
	metadata:
	name: restricted
	annotations:
	seccomp.security.alpha.kubernetes.io/allowedProfileNames: 'docker/default'
	apparmor.security.beta.kubernetes.io/allowedProfileNames: 'runtime/default'
	seccomp.security.alpha.kubernetes.io/defaultProfileName: 'docker/default'
	apparmor.security.beta.kubernetes.io/defaultProfileName: 'runtime/default'
	spec:

	export default [
	"Reticulating splines...",
	"Generating witty dialog...",
	"Swapping time and space...",
	"Spinning violently around the y-axis...",
	"Tokenizing real life...",
	"Bending the spoon...",
	"Filtering morale...",
	"Don't think of purple hippos...",
	"We need a new fuse...",