We mentioned letting users add new aliases from anywhere without having to open any of the dotfiles themselves. This doesn't seem like it would be too hard.

concept/plan:

setup:

[x] make .bash_alias << should we name this something else?
[x] check if alias is a reserved name (yes, it's very reserved)

usage:

add alias "aliasname"="command" or add "aliasname" "command" Pick the second for now; we don't have enough syrup here for waffling. Final syntax: addalias aliasname="commands go here"

[x] figure out how to make spaces work in command
[x] decide whether you'll support spaces in aliasname (this part's optional)

implementation:

[x] write the alias to a new file (.usr_aliases?)
[x] include .usr_aliases in something that will get run when you source the .bashrc (in the bottom of .bash_alias)
[x] source the .bashrc or whatever it is (I'd like to use the src command from .cds_nav)

side of fries:

[ ] we should really decide how we're going to include other functions . . . we should be able to force include dependencies from sibling files that we wrote. What if I want to use .cds_nav? See #41.
[ ] decide if you want tab completion for commands. See #43.

GiselleSerate / myaliases

add new alias #37

concept/plan:

setup:

usage:

implementation:

side of fries: