Skip to content

Latest commit

 

History

History
59 lines (37 loc) · 2.04 KB

INSTALL.md

File metadata and controls

59 lines (37 loc) · 2.04 KB

Welcome

Getting Started

It's going to help me to help you if if :

  1. Your local copy of the repo has a top level directory 'dopamine-2022' with the Makefile at that level.

  2. You can have a directory tree $HOME/local/i3/{bin,share} and put the bin folder on your $PATH.

  3. You can have a directory tree /dev/shm/$USER/i3/ in shared memory.

I've tried not to make any the above mandatory, and have made many things configurable, it's going t obe simpler if we s tick wit the d efalts for a while. I'v tried not to bring down the wrath of company IT people on anyone so burdened. If have done something stupid, be kind.

Use $HOME .inputrc with bash

\#!/bin/bash
\#
\# dot-inputrc
\#

"\e[A": history-search-backward
"\e[B": history-search-forward
set show-all-if-ambiguous on
set completion-ignore-case on
"\e[1;5C": forward-word
"\e[1;5D": backward-word

#
# Done.
#

You're going to type many repetitive commands. Install the above, without indent, as '$HOME/.input.rc'. If you want to repeat a command, type the first few characters and press Up. You'll see a command like the one you want. If it issn't quite right, press Up again and repeat, or edit the line.

The real payback comes when you're setup to save your command history for 1k, 100k, 1M lines. You'll never lose any tricks or magic you've done in the past. With ffmpeg commands it's awesome.

Quick start

  1. cd to the 'dopamine-2022' directory

  2. type 'make wizard''

  3. if make stops on error, type 'cat .log; cat bin/.log'. Do what ShellCheck says, and start over.

What make does

  1. Text substitutions using 'sed' for the '###INSERT...HERE###' functionality. The Makefile does this in-place so takes a copy 'foo.inc' of the original 'foo'.

  2. Sanity checks on bash scripts using ShellCheck. Make stops on error. For file 'bar', make writes errors to 'bar.log', which will be recreated empty beforehand so that installation depends on 'bar.log'.

  3. Binaries and configuration are installed in their runtime locations with runtime permissions.