`.zshenv` is read for all shells, interactive or not, making it the best
place to set variables that always apply. Unfortunately, it cannot be
kept in `ZDOTDIR`, since that variable has to be set in that same
script. To work around this, the "real" `.zshenv` can source the one in
`ZDOTDIR`.
* `@testvm::cleanup`: Deletes (after optionally powering off) test VMs
matching a pattern
* `@testvm::connect`: Connects to test VM using SSH
* `@testvm::delete`: Powers off and deletes a specific test VM
* `@testvm::sftp`: Connects to a test VM using SFTP
Tools (such as VSCode) can read and use environment variables from a
file in the current working directory named `.env`. Unfortunately,
these tools are not exactly compatible with shell syntax, as they do not
correctly process lines starting with `export`.
The `dotenv` function will read a `.env` file from the current working
directory and then export all of the variables it defines. This allows
the `.env` file to define the variables without "exporting" them, making
them compatible with VSCode et al, but still allowing the same
environment variables to be set in the shell and its child processes.
The `.zprofile` file is sourced by ZSH when the shell is run as a login
shell. The `.zprofile.local` file, if it exists, is sourced by the main
`.zprofile` script, and is the best place for unversioned per-machine
changes.
The `window_title` variable can be set to completely override the title
of the terminal window. Alternatively, if the `term_name` variable is
set, it will be prepended to the default window title.
Updating to the version of .zshrc on Tau Scorpii. This enhanced version
has a couple of improvements:
* Aliases moved to a separate file for easier maintenance
* Auto-discovery of functions on fpath
Dustin