|author||Tom Ryder <firstname.lastname@example.org>||2015-06-10 10:44:18 +1200|
|committer||Tom Ryder <email@example.com>||2015-06-10 10:44:18 +1200|
|parent||Print verse(1) output on login but only once a day (diff)|
Stuff that prints messages really only needs to be done for my primary login shell
Diffstat (limited to 'README.markdown')
1 files changed, 5 insertions, 5 deletions
diff --git a/README.markdown b/README.markdown
index 4f50e384..d39e2ef6 100644
@@ -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