jcburley / unixhome Goto Github PK

​Put $HOME/bin on $PATH so lein command actually works, and ensure Emacs picks up $PATH from the environment even when invoked via the GUI (versus a terminal).

I keep forgetting how exactly to do this, and it's non-trivial to type, so basically do this for each (non-option) argument:

cp --force --preserve=all --backup=t $1 $1

Support options so -v works.

Add explicit --path= option to specify the path, so an empty path can be handled within $(...) without having to use eval.

Maybe also support --pathvar= to name a var that path itself expands?

Create and install man page.

Have both --help and man page explain possible need to first test for path itself being in $PATH, or don't assign results of $(path ...) (or equivalent) to the $PATH or similar variable directly, instead to a temp var that is then checked for the empty string (which would mean path itself didn't run, i.e. wasn't found, in most cases), assigning to the ultimate variable only if non-empty.

Some info is provided here, but I've been able to get it to work -- the symptom being that git commit -a (in my case) immediately exits, complaining about an (aborted) empty commit message, before the editor has actually launched, nevermind editing, saving, and exiting happened:

https://www.emacswiki.org/emacs/EmacsMsWindowsIntegration

For now, just use git commit -m "" and similar.

​Emacs 25 has trouble with eldoc-mode: clojure-emacs/cider#1105

This is "vanilla" Emacs 25.3:

Warning (initialization): An error occurred while loading ‘/Users/craig/.emacs’:

Symbol's function definition is void: global-company-mode

To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file.  Start Emacs with
the ‘--debug-init’ option to view a complete error backtrace.

Details on version:

GNU Emacs 25.3.1 (x86_64-apple-darwin13.4.0, NS appkit-1265.21 Version 10.9.5 (Build 13F1911))
 of 2017-09-12

That means changes to etc/bashrc and such must be copied to e.g. ~/.bashrc manually.

This could be addressed by using mklink in lieu of ln (if the system supports that and when running on Windows).

Or, .Setup/bash could put a one-liner, in each of the appropriate files, that sources its git-controlled target directly.