Philipp "Flipsi" Moers flipsi

Rich Already Answered That!

A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats.

How to use:

The link in the table of content jumps at the copy of the answer on this page.
The link on the answer itself points back at the original post.

Table of Content

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

	#!/usr/bin/env python
	# vim: set fileencoding=utf-8
	#
	# USAGE:
	# Back up your tmux old config, run the script and redirect stdout to your conf
	# file. Example:
	#
	# $ cp ~/.tmux.conf ~/.tmux.conf.orig
	# $ python ./tmux-migrate-options.py ~/.tmux.conf.orig > ~/.tmux.conf
	#

	--- Actions ---
	$Copy <M-C>
	$Cut <M-X> <S-Del>
	$Delete <Del> <BS> <M-BS>
	$LRU
	$Paste <M-V>
	$Redo <M-S-Z> <A-S-BS>
	$SearchWeb <A-S-G>
	$SelectAll <M-A>
	$Undo <M-Z>

	#!/usr/bin/env bash

	#
	# This is sp, the command-line Spotify controller. It talks to a running
	# instance of the Spotify Linux client over dbus, providing an interface not
	# unlike mpc.
	#
	# Put differently, it allows you to control Spotify without leaving the comfort
	# of your command line, and without a custom client or Premium subscription.
	#

Philipp "Flipsi" Moers flipsi

Rich Already Answered That!

Table of Content

Better local require() paths for Node.js

Problem

Possible solutions