Matthew Tylee Atkinson matatk

(generated by chatgpt 4o and reviewed/edited by claude 3.5 sonnet, YMMV)

| Feature | Bash | Elvish | NuShell | Murex | Es Shell | Fish | Xonsh | PowerShell | Oil | Ion | |----------------------------------|-----------------------------------------------|-----------------------------------------------|----------------------------------------------|----------------------------------------------|----------------------------------------------|----------------------------------------------|----------------------------------------------|----------------------------------------------|-------------------------

Semantic Highlighting in Neovim

What is Semantic Highlighting?
Default Highlighting
Using LspTokenUpdate for Complex Highlighting
- Highlighting Based on More Than One Modifier
Dealing with Ambiguity

Vim has a Terminal Mode!

Since v8.1 (May 2018), Vim has shipped with a built-in terminal. See https://vimhelp.org/terminal.txt.html or type :help terminal for more info.

Why use this? Mainly because it saves you jumping to a separate terminal window. You can also use Vim commands to manipulate a shell session and easily transfer clipboard content between the terminal and files you're working on.

Key Bindings

(To be improved)

Requirements

httpie (which provides the http command) — pip install httpie

Setup

Save the git-branch-protection.sh as git-branch-protection somewhere in your path (something like ~/bin or ~/.local/bin if you already use it)
Generate a GitHub token and save it as ~/.config/github_token.

I personally prefer [Semver][]. I think it's reasonable, simple, and makes sense. But as a good Haskell citizen, I'd like to be [PVP][]-compliant as well. Here is a bit of a graphic showing how the two systems are almost the same:

PVP:            A . B     . C     . ...
Semver:             Major . Minor . Patch
                    ^       ^       ^
                    |       |       |
                    |       |       ` increment for other changes
                    |       |
                    |       ` increment on non-breaking change

A vision for data interchange in Elm

How do you send information between clients and servers? What format should that information be in? What happens when the server changes the format, but the client has not been updated yet? What happens when the server changes the format, but the database cannot be updated?

These are difficult questions. It is not just about picking a format, but rather picking a format that can evolve as your application evolves.

Literature Review

By now there are many approaches to communicating between client and server. These approaches tend to be known within specific companies and language communities, but the techniques do not cross borders. I will outline JSON, ProtoBuf, and GraphQL here so we can learn from them all.

	format = """
	[\uE0B6](fg:#1C4961)[$directory](bg:#1C4961)[\uE0B0](fg:#1C4961 bg:#2F79A1)$git_branch[\uE0B0](fg:#2F79A1 bg:#3A95C7)$git_status[\uE0B0](#3A95C7 bg:#40A9E0)$time[\uE0B0](#40A9E0 bg:none) $all$character """

	add_newline = true

	[directory]
	style = "bg:#1C4961 fg:white"

	[git_branch]
	format = "[ $symbol$branch ]($style)"

	// Copyright 2021 Google LLC.
	// SPDX-License-Identifier: Apache-2.0

	let videos = [
	{
	url: 'https://interactive-examples.mdn.mozilla.net/media/cc0-videos/flower.mp4',
	type: 'video/mp4',
	}, {
	url: 'https://interactive-examples.mdn.mozilla.net/media/cc0-videos/flower.webm',
	type: 'video/webm',

	" Open Netrw on the directory of the current file
	nnoremap <leader>dd :Lexplore %:p:h<CR>

	" Toggle the Netrw window
	nnoremap <Leader>da :Lexplore<CR>

	if &columns < 90
	" If the screen is small, occupy half
	let g:netrw_winsize = 50
	else

	use std::fmt;

	#[derive(Clone, Debug)]
	pub struct DateTime {
	/// Seconds after the minute - [0, 59]
	pub sec: i32,
	/// Minutes after the hour - [0, 59]
	pub min: i32,
	/// Hours after midnight - [0, 23]
	pub hour: i32,