Matteo Landi iamFIREcracker

I use tmux splits (panes). Inside one of these panes there's a Vim process, and it has its own splits (windows).

In Vim I have key bindings C-h/j/k/l set to switch windows in the given direction. (Vim default mappings for windows switching are the same, but prefixed with C-W.) I'd like to use the same keystrokes for switching tmux panes.

An extra goal that I've solved with a dirty hack is to toggle between last active panes with C-\.

Here's how it should work:

rage-quit support for bash

HOW TO INSTALL

Put flip somewhere in your $PATH and chmod a+x it.

Copy fuck into ~/.bashrc.

OBSOLETE

This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.

I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.

Fixing npm On Mac OS X for Homebrew Users

Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

Learning FP the hard way: Experiences on the Elm language

by Ossi Hanhinen, @ohanhi

with the support of Futurice 💚.

Licensed under CC BY 4.0.

Editorial note

Interactive Debugging on Github Actions

Did you ever run into some issue where a job would behave slightly different in you CI environment than on your local machine? Did you ever wish you could run just a few commands in a shell on your build machine?

These are, of course rhetorical questions. And if you're using Github Actions to run your CI jobs, you'll have noticed that this use case is not supported at all. Can't create a nice walled garden if anyone could just run a CI job, after all. There are some workarounds (e.g. https://github.com/nektos/act), but since they're not officially supported they can be a bit unstable. Also, even they usually don't reproduce the exact environment found on github's servers.

	var net = require("net");

	process.on("uncaughtException", function(error) {
	console.error(error);
	});

	if (process.argv.length != 5) {
	console.log("usage: %s <localport> <remotehost> <remoteport>", process.argv[1]);
	process.exit();
	}

	#!/bin/sh
	#
	# Query a property from the terminal, e.g. background color.
	#
	# XTerm Operating System Commands
	# "ESC ] Ps;Pt ST"

	oldstty=$(stty -g)

	# What to query?

	#!/usr/bin/env bash

	# This function lets you easily create series of commands into a single call
	# It will print each successive command, run it and, as long as it returned
	# with code 0, continue to the next step.
	# If any step fails, it will stop and let you pick it back up after you fix the
	# issues.
	#
	# Example of script using this function:
	# !/usr/bin/env bash

	function mapSeries(arr) {
	if (!Array.isArray(arr)) throw new Error('mapSeries requires an Array');
	const length = arr.length;
	const results = new Array(length);

	arr.reduce((chain, item, i) => {
	return chain.then(() => item).then(val => results[i] = val);
	}, Promise.resolve())
	.then(() => results);
	}