Skip to content

Latest commit

 

History

History
31 lines (21 loc) · 1.32 KB

README.md

File metadata and controls

31 lines (21 loc) · 1.32 KB

env.d

It is exactly as insane and silly as it looks. It also may come with some risk depending on how the computer permissions are set up.

Inspiration for this came from

Getting Started

Step 1 -- Install Script

Add the following snippet to a POSIX compliant shell startup files:

if [ -d "$XDG_CONFIG_HOME/sh/env.d" ]; then
  for i in $XDG_CONFIG_HOME/sh/env.d/* ; do
    if [[ -f $i && -r $i ]] ; then . $i ; fi
  done ; unset i
fi

Step 2 -- Fix all the S#!T

Fix the many things that just broke due to your naïve attempt to micromanage your operating system into behaving.

On macOS this included making sure $XDG_CONFIG_HOME is set at startup one way or another. Take note that if you don't have the permissions correct, you will have a bad day when someone or more likely something decides to delete modify you bodge. Your first sign of this, depending on how aggressively you modified your config, will be that none of your programs are working correctly.

Step 3 -- Regret

Perhaps now is the time to reconsider your trajectory and all of the decisions that led you to this point.