aboutsummaryrefslogtreecommitdiff
path: root/README.markdown
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2015-06-10 10:44:18 +1200
committerTom Ryder <tom@sanctum.geek.nz>2015-06-10 10:44:18 +1200
commit69dabe5a87f556505b6dd05ea2250df293b4889b (patch)
treeffefcd8b0d4ac4d6d61beea8dd4ac67031f79b99 /README.markdown
parentPrint verse(1) output on login but only once a day (diff)
downloaddotfiles-69dabe5a87f556505b6dd05ea2250df293b4889b.tar.gz
dotfiles-69dabe5a87f556505b6dd05ea2250df293b4889b.zip
Instate .bash_profile.d
Stuff that prints messages really only needs to be done for my primary login shell
Diffstat (limited to 'README.markdown')
-rw-r--r--README.markdown10
1 files changed, 5 insertions, 5 deletions
diff --git a/README.markdown b/README.markdown
index 4f50e384..d39e2ef6 100644
--- a/README.markdown
+++ b/README.markdown
@@ -97,11 +97,11 @@ by `.profile` are saved in `.profile.d` and iterated on login for ease of
management. All of these boil down to exporting variables appropriate to the
system and the software it has available.
-My `.bash_profile` calls `.profile` for variable exports, and then runs
-`.bashrc` for interactive shells. Subscripts are kept in `.bashrc.d`, and all
-are loaded for the creation of any new interactive shell. The contents of this
-directory changes all the time depending on the host, and only specific scripts
-in it are versioned.
+My `.bash_profile` calls `.profile` for variable exports, runs subscripts in
+`.bash_profile.d`. It then runs `.bashrc`, which only applies for interactive
+shells; subscripts are loaded from `.bashrc.d`. interactive shell. The contents
+of this directory changes all the time depending on the host, and only specific
+scripts in it are versioned.
My interactive and scripting shell of choice is Bash; as a GNU/Linux admin who
ends up installing Bash on \*BSD machines anyway, I very rarely have to write