##############
+# make our functions available to the aliases.
+#hmmm: should this be necessary? will it even work?
+source "$FEISTY_MEOW_SCRIPTS/core/functions.sh"
+
+##############
+
# call the generated aliases file, if it exists.
# we do this first so that our core aliases get a chance to override the aliases
# based on scripts.
# some really eccentric feisty meow aliases...
+# launches a bash session in the background using the screen command.
+define_yeti_alias bashido='screen -L -S bashido -d -m bash'
+
# says goodbye when leaving a shell.
define_yeti_alias bye='. $FEISTY_MEOW_SCRIPTS/processes/goodbye.sh'
+
define_yeti_alias cputemp='acpi -t'
+
# makes root user's home directory's permissions right.
define_yeti_alias reroot='chown -R root:root /root'
-# yes, these are really helpful...
+
+# yes, these what/who/why functions are really helpful...
define_yeti_alias whoareyou='echo -e "Hello, I am a computer named $(hostname)\nand I am very pleased to meet you."'
define_yeti_alias whereami='echo whoa dude, try not to think about it...'
define_yeti_alias why='echo We all wonder what the point of the universe is at times. If you figure it all out, please write us.'