UnixHome

My $HOME directory for Unixy OSes

Before Cloning Me

Per-OS Preparation

Mac OS X

• Establish your login shell; these instructions assume Bash, so (if necessary) chsh -s /bin/bash and login a new shell to use going forward.
• Install GitHub Desktop via https://desktop.github.com/ and login
• Install homebrew ("brew")
• Install GNU stuff via: brew install coreutils findutils gnu-tar gsed gnutls gnu-indent gnu-getopt gawk grep bash-completion zsh-completion emacs
  • NOTE: This seems to take awhile before the new Emacs is actually invoked (try emacs --version)
  • Maybe try $ hash -r first, or log in a new terminal and try it there
• Per the output of brew, to have various commands such as tar (not only when prefixed with g, e.g. gtar) run GNU version (instead of BSD tar), edit ~/.profile to specify e.g. PATH="/usr/local/opt/gnu-tar/libexec/gnubin:$PATH"
• If the system is under your control, make sure system name (as returned by hostname) is as desired for .emacs.d/systems/:
  • sudo scutil --set HostName xxx
  • sudo scutil --set LocalHostName xxx
  • sudo scutil --set ComputerName xxx

All OSes

Add local account's public RSA key (on Linux, this will be in ~/.ssh/id_rsa.pub, or do ssh-keygen -t rsa to create it) as an SSH key to https://github.com account. (This might not be necessary if one uses GitHub Desktop.)

Clone Me

Do either of these:

• $ cd ~; git clone [email protected]:jcburley/UnixHome.git .unixhome
• Use GitHub Desktop
  • Change the desired target directory to specify ~/.unixhome (e.g. remove intermediate components, lowercase capitalized "UnixHome", etc.)

After Cloning Me

$ cd ~/.unixhome/Setup
$ ./git
$ ./bash
$ ./emacs
$ cd ../bin
$ ./install.sh  # Installs to ~/bin: bash-for-emacs emacs install-go.sh path rssh settitle
$ sudo ./install.sh --system # Optional, instead of './install.sh', to install to /usr/local/bin
$ cd ../build; ./install.sh  # OPTIONAL, if the 'build' command is desired

Why Install to /usr/local/bin?

Installing useful tools into /usr/local/bin, instead of ~/bin, by using (say) the --system option with ./install.sh in a directory, simplifies access via e.g. ssh user@system <toolname>. E.g. on my Ubuntu 16.04 system, I can't figure out how to add ~/bin to $PATH such that it is effective when searching for toolname in such an ssh command. (Seems like /bin/sh, which is dash, gets invoked by sshd only to initialize things, not to establish an environment that's then passed to the toolname when it is actually executed. No amount of playing around with /etc/environment, adding PermitUserEnvironment yes to /etc/ssh/sshd_config, putting definitions in ~/.ssh/rc, etc., seemed to have any effect on the environment for toolname despite it having various effects on the output if toolname was something like env.)

Sanity-check

Make sure that etc/bashrc and etc/bash_profile get run by various methods of logging in, but do not get caught in a loop running each other (or being run by outside scripts).

• ~/.profile typically doesn't try to run .bashrc or anything else, but Ubuntu 16.04, or something I installed above it on an Ubuntu machine, had one that did.
• __git_ps1 not being found at each prompt is a symptom of this mechanism breaking, since etc/git-prompt.sh needs to be sourced from ${UNIXHOME}, which ~/.bash_profile defines only after invoking ~/.profile (which could perhaps be changed, but it's really not clear to me which startup script should be responsible for what actions across all OSes and shells, so the order in which things should be done is also unclear).

Start up GNU Emacs, and confirm:

• Personal bindings (such as C-c w to compare windows) work
• Finding a file (even if non-existent) such as foo.joke brings up Clojure and related modes (might have to package-install them)

To Keep Installation Up To Date

Per-OS Maintenance

Mac OS X

brew upgrade