`working_dir` verb attribute

It makes it possible to set the working dir of a new executable to
something different than the current directory. For example

working_dir: "{directory}/.git"

Fix #396

1 files changed, 2 insertions, 1 deletions

diff --git a/website/docs/conf_verbs.md b/website/docs/conf_verbs.md
index 92da2d1..3d465d9 100644
--- a/website/docs/conf_verbs.md
+++ b/website/docs/conf_verbs.md
@@ -39,7 +39,8 @@ shortcut | | an alternate way to call the verb (without the arguments part)
 leave_broot | `true` | whether to quit broot on execution
 from_shell | `false` | whether the verb must be executed from the parent shell (needs `br`). As this is executed after broot closed, this isn't compatible with `leave_broot = false`
 apply_to | | the type of selection this verb applies to, may be `"file"`, `"directory"` or `"any"`. You may declare two verbs with the same key if the first one applies to only files or only directories
-set_working_dir | `false` | whether the working dir of the process must be set to the currenly selected directory
+working_dir | | the working directory of the external application, for example `"{directory}"` for the closest directory (the working dir isn't set if the directory doesn't exist)
+set_working_dir | `false` | whether the working dir of the process must be set to the currenly selected directory (it's equivalent to `workding_dir: "{directory}"`)
 auto_exec | `true` | whether to execute the verb as soon as it's key-triggered (instead of waiting for <kbd>enter</kbd>)
 
 The execution is defined either by `internal`, `external` or `cmd` so a verb must have exactly one of those (for compatibility with older versions broot still accepts `execution` for `internal` or `external` and guesses which one it is).