Available built in templates are

- **source**: source each filename in a plugin.

- **source**: source each file in a plugin.

- **PATH**: add the plugin directory to the `PATH` variable.

- **FPATH**: add the plugin directory to the `FPATH` variable.

- **path**: add the plugin directory to the `path` variable.

```toml

[templates]

source = { value = 'source "{{ filename }}"', each = true }

source = { value = 'source "{{ file }}"', each = true }

PATH = 'export PATH="{{ dir }}:$PATH"'

FPATH = 'export FPATH="{{ dir }}:$FPATH"'

path = 'path=( "{{ dir }}" $path )'

```

The `each` value, as used in the `source` template above, specifies that the

template should be applied to each matched filename for the plugin. This

defaults to `false`.

template should be applied to each matched file for the plugin. This defaults to

`false`.

### Custom templates

- **A directory.** In git sources this is the location of the cloned repository,

for local sources, it is the directory specified. This directory can be used

in templates with `{{ dir }}`.

- **Zero or more filenames.** These are the matched files in the plugin

directory either discovered using the the global `match` field or specified as

a plugin option with `use`. These can be used in templates using `{{ filename

}}`.

- **Zero or more files.** These are the matched files in the plugin directory

either discovered using the the global `match` field or specified as a plugin

option with `use`. These can be used in templates using `{{ file }}`.

You can use the following global information in templates

```toml

[templates]

function = { value = 'ln -sf "{{ filename }}" "~/.zsh/functions/{{ name }}"', each = true }

function = { value = 'ln -sf "{{ file }}" "~/.zsh/functions/{{ name }}"', each = true }

```

It can then be applied to the plugin like this