GitLab

On systems where the shell cannot be changed because of a strict
security policy, ssh-agent will use the syntax of whatever the
default $SHELL is.
For instance, if the default shell is tcsh, ssh-agent will use the
c-shell style (setenv).

This change forces ssh-agent to use bourne-style syntax since that
has to be later interpreted by zsh. Consequently, the environment
file will contain `export' statements from now on (instead of
`setenv').

This change is important when ssh-add is not inside /usr/bin e.g.
on NixOS.
Signed-off-by: Maximilian Güntner <code@maschinenpsychologe.de>

On an OS X laptop, the variable `$HOST` changes a lot depending
on what wifi network you're connected to.  This causes a lot
of `~/.ssh/environment-$HOST` files to be created and
causes multiple ssh-agents to created.

Instead, use `scutil --get ComputerName` to get something
more stable.

By default, ssh-agent stores identities forever. It has an option to
set a maximum lifetime for identites (useful to expire passphrase protected
keys). Allow this option to be set using:

zstyle :omz:plugins:ssh-agent lifetime <time>

OpenBSD doesn't have -ef flags for ps. Both linux and OpenBSD have -x flags which works just as greate here

Reorganizing plugins so that each plugin has it's own directory now so that any plugin-specific functions can be bundled within there.

Implement a simple module that automatically launches the ssh-agent when you login and
adds your default key.

Useful for anyone that does remote work and thus doesn't have access to a keychain tool.