# Autoenv for Zsh
-zsh-autoenv automatically sources `.env` files, typically used in project
-root directories.
+zsh-autoenv automatically sources (known/whitelisted) `.autoenv.zsh` files,
+typically used in project root directories.
It handles "enter" and leave" events, nesting, and stashing of
variables (overwriting and restoring).
## Features
- Support for enter and leave events, which can use the same file.
- By default `.env` is used for entering, and `.env_leave` for leaving.
- - Asks for confirmation / authentication before sourcing a `.env` file, and
- remembers whitelisted files by its hash.
+ By default `.autoenv.zsh` is used for entering, and `.autoenv_leave.zsh`
+ for leaving.
+ - Interactively asks for confirmation / authentication before sourcing an
+ unknown `.autoenv.zsh` file, and remembers whitelisted files by their
+ hashed content.
- Test suite.
- Written in Zsh.
### Variable stashing
-You can use `autostash` in your `.env` files to overwrite some variable, e.g.
-`$PATH`. When leaving the directory, it will be automatically restored.
+You can use `autostash` in your `.autoenv.zsh` files to overwrite some
+variable, e.g. `$PATH`. When leaving the directory, it will be automatically
+restored.
- % echo 'echo ENTERED; autostash FOO=changed' > project/.env
+ % echo 'echo ENTERED; autostash FOO=changed' > project/.autoenv.zsh
% FOO=orig
% cd project
Attempting to load unauthorized env file!
- -rw-rw-r-- 1 user user 36 Mai 6 20:38 /tmp/project/.env
+ -rw-rw-r-- 1 user user 36 Mai 6 20:38 /tmp/project/.autoenv.zsh
**********************************************
The varstash library has been taken from smartcd, and was optimized for Zsh.
-## Writing your .env file
+## Writing your .autoenv.zsh file
### `autoenv_source_parent()`
-zsh-autoenv will stop looking for `.env` files after the first one has been
-found. But you can use the function `autoenv_source_parent` to source a
-parent `.env` file from there.
+zsh-autoenv will stop looking for `.autoenv.zsh` files after the first one has
+been found. But you can use the function `autoenv_source_parent` to source a
+parent `.autoenv.zsh` file from there.
## Installation
### AUTOENV\_FILE\_ENTER
Name of the file to look for when entering directories.
-Default: `.env`
+Default: `.autoenv.zsh`
### AUTOENV\_FILE\_LEAVE
Name of the file to look for when leaving directories.
Requires `AUTOENV_HANDLE_LEAVE=1`.
-Default: `.env_leave`
+Default: `.autoenv_leave.zsh`
### AUTOENV\_LOOK\_UPWARDS
-Look for .env files in parent dirs?
+Look for zsh-autoenv "enter" files in parent dirs?
Default: `1`
Default: 0
-### `AUTOENV_DEBUG`
+### AUTOENV\_DEBUG
Enable debugging. Multiple levels are supported (max 2).
Default: `0`
## History
-This started as a optimized version of
-[autoenv](https://github.com/kennethreitz/autoenv) for Zsh, but grew a lot of
-functionality on top of it (inspired by
-[smartcd](https://github.com/cxreg/smartcd)).
+This started as an optimized version of the bash plugin
+[autoenv](https://github.com/kennethreitz/autoenv) but for Zsh, and grew a lot
+of functionality on top of it (inspired by [smartcd]).
-The code was initially based on [Joshua Clayton](https://github.com/joshuaclayton)'s work.
+The code was initially based on
+[@joshuaclayton](https://github.com/joshuaclayton)'s dotfiles.
+In September 2013 [@Tarrasch](https://github.com/Tarrasch) packaged it into a
+nice [antigen]-compatible unit with integration tests. Since November 2014,
+[@blueyed](https://github.com/blueyed) took over and added many many nice
+features, mainly inspired by [smartcd].
+
+[antigen]: https://github.com/Tarrasch/antigen-hs
+[smartcd]: https://github.com/cxreg/smartcd