mirrors/dotdrop
1
0
Fork 0
mirror of https://github.com/deadc0de6/dotdrop.git synced 2026-02-05 08:33:49 +00:00
Code Activity

fix links

Browse Source
This commit is contained in:
deadc0de6
2020-09-15 22:57:13 +02:00
parent e51bacc217
commit 4f186c3d27
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/config-details.md
View File

@@ -530,7 +530,7 @@ import_configs:
## Dynamic dotfile paths
Dotfile source (`src`) and destination (`dst`) can be dynamically constructed using
defined variables ([variables and dynvariables](#variables)).
defined variables ([variables and dynvariables](config.md#variables)).
For example to have a dotfile deployed on the unique firefox profile where the
profile path is dynamically found using a shell oneliner stored in a dynvariable:
@@ -551,7 +551,7 @@ Make sure to quote the path in the config file.
## Dynamic actions
Variables ([config variables and dynvariables](#variables)
Variables ([config variables and dynvariables](config.md#variables)
and [template variables](templating.md#template-variables)) can be used
in actions for more advanced use-cases.
@@ -585,7 +585,7 @@ Make sure to quote the actions using variables.
## Dynamic transformations
As for [dynamic actions](#dynamic-actions), transformations support
the use of variables ([variables and dynvariables](#variables)
the use of variables ([variables and dynvariables](config.md#variables)
and [template variables](templating.md#template-variables)).
A very dumb example:

6
docs/config.md
View File

@@ -20,7 +20,7 @@ or by defining the `DOTDROP_CONFIG` environment variable.
Multiple variables can be used within the config file to
parametrize following elements of the config:
* dotfiles `src` and `dst` paths (see [Dynamic dotfile paths](#dynamic-dotfile-paths))
* dotfiles `src` and `dst` paths (see [Dynamic dotfile paths](config-details.md#dynamic-dotfile-paths))
* external path specifications
* `import_variables`
* `import_actions`
@@ -29,8 +29,8 @@ parametrize following elements of the config:
`actions` and `transformations` also support the use of variables
but those are resolved when the action/transformation is executed
(see [Dynamic actions](#dynamic-actions),
[Dynamic transformations](#dynamic-transformations) and [Templating](templating.md)).
(see [Dynamic actions](config-details.md#dynamic-actions),
[Dynamic transformations](config-details.md#dynamic-transformations) and [Templating](templating.md)).
Following variables are available in the config files: