# the "fredme" macro enables the feisty_meow environment.
alias fredme='source "$FEISTY_MEOW_APEX/scripts/core/launch_feisty_meow.sh"'
-# synonym for fredme.
+# synonym for fredme which makes more sense to most people.
alias feistyme='source "$FEISTY_MEOW_APEX/scripts/core/launch_feisty_meow.sh"'
# if not commented out, then feisty meow will run all the unit tests during builds.
Note that this actually modifies ~/.bashrc. This step is only needed once.
# bash /opt/feistymeow.org/feisty_meow/scripts/core/connect_feisty_meow.sh
+| For the root user, you can pass a flag '--root' to the connect_feisty_meow
+| script. This will add an alias for 'feistyme' which loads the feisty meow
+| scripts on demand (instead of automatically upon login).
+
Load the script environment into the current shell. This can be done for
any new shell. This is idempotent, so it does no harm to run it again.
Note that you should not need this step if you connected feisty meow to
# notes are individual files of tasks, usually, although some are combined.
analyze_hierarchy_and_report ~/cloud/grunty_notes "grunty notes (externalities)"
+# web site development tasks.
+analyze_hierarchy_and_report ~/cloud/webular "web design (ideas and tasks)"
+
# feisty notes are about feisty meow(r) concerns ltd codebase development.
analyze_hierarchy_and_report ~/cloud/feisty_notes "feisty meow notes (mondo coding)"
##############
-# remove the fredization macro if it was defined, helping to avoid running
-# the shell scripts twice for users like root that don't always load this
-# stuff.
-unalias fredme &>/dev/null
-unalias feistyme &>/dev/null
+# remove the "fredization" or "feistymeowization" macros if they're defined,
+# which reduces the chance of loading the shell environment twice for users
+# like root that don't load feisty meow automatically.
+unalias fredme feistyme &>/dev/null
##############
>> "$HOME/.bashrc"
echo "Feisty Meow is now configured in '~/.bashrc' for standard users."
else
- # stuff the root user init file into .bashrc. this one doesn't automatically load
- # feisty meow. instead, it provides a fredme macro to load the feisty meow scripts.
- # fredme comes from the main author being fred t. hamster. we have since added a
- # feistyme macro too, to be less personalized...
+ # stuff the root user init file into .bashrc. this one doesn't
+ # automatically load the feisty meow scripts. instead, there is a macro
+ # (uhh, an alias) that loads the feisty meow scripts. the 'fredme' macro
+ # comes from the main author of feisty meow, named fred t. hamster. we
+ # have since added a 'feistyme' macro too, to be slightly less
+ # idiosyncratic, as if that were possible.
cat $FEISTY_MEOW_APEX/infobase/feisty_inits/dot.bashrc-root |
sed -e \
"s?FEISTY_MEOW_APEX=\".*\"?FEISTY_MEOW_APEX=\"$FEISTY_MEOW_APEX\"?" \
then try openshot. it also supports simple saving with different quality levels, which
lets you drop a bunch of size at the expense of the picture. sometimes needed.
+---------------------------
+music collection management
+---------------------------
+
+dupeguru:
+found this to be pretty helpful in finding my duplicate songs. it is able to analyze
+when the files are the same, even if their names don't match.
+check: did it even compare by metadata? not remembering currently.
+
+fdupes:
+another useful tool for finding duplicate tracks in a music collection, but relies on exact
+matches in the names(?). was not so powerful as dupeguru, but still useful.
+
+
+
+