Shell Configuration

[rye]

One aspect of this project that we haven't really covered is shell configurations.

My plan is to imitate what we did with Emacs, but this time for a shell configuration.

Generally, the process to implement this is as follows:

• We would implement something like a ~/.profile file meant to be loaded independently of by which app, to normalize environment variables.
  • From this, we would move on to implementing a smarter and smarter configuration system so that it is more dynamic and smart.
  • We could consider implementing this with a large number of debugging traces that we can turn off when we're done but still use for testing.
• From this, we would implement some (much smaller) configurations for each of the different shells we use.

A question to be answered by @cg505, (also @Sammidysam, and @samontea):

• Should we set PS1? Or should that be user-configured locally?
  • If it should be set by the user, how? (cc Machine-Local Configuration #30)

[cg505]

We should set the prompt but allow it to be override on a per-user basis, similarly to the emacs config.