summaryrefslogtreecommitdiffstats
path: root/docs/Custom_Command_Keybindings.md
diff options
context:
space:
mode:
authorsportshead <32637656+sportshead@users.noreply.github.com>2022-07-28 18:57:16 +0800
committersportshead <32637656+sportshead@users.noreply.github.com>2022-07-28 18:57:16 +0800
commit168fbe0a6c25390a6982536254cfb0ff68a06b4a (patch)
treedbf5938dad5c70553575ee5484bc1fda2bd7e338 /docs/Custom_Command_Keybindings.md
parente1f41b653c8a84b551500b5df472de46c87379cb (diff)
Add showOutput option to docs
Diffstat (limited to 'docs/Custom_Command_Keybindings.md')
-rw-r--r--docs/Custom_Command_Keybindings.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/Custom_Command_Keybindings.md b/docs/Custom_Command_Keybindings.md
index 47b9d8f97..ac61c1282 100644
--- a/docs/Custom_Command_Keybindings.md
+++ b/docs/Custom_Command_Keybindings.md
@@ -77,6 +77,7 @@ For a given custom command, here are the allowed fields:
| loadingText | text to display while waiting for command to finish | no |
| description | text to display in the keybindings menu that appears when you press 'x' | no |
| stream | whether you want to stream the command's output to the Command Log panel | no |
+| showOutput | whether you want to show the command's output in a gui prompt | no |
### Contexts
@@ -159,7 +160,7 @@ If your custom keybinding collides with an inbuilt keybinding that is defined fo
### Debugging
-If you want to verify that your command actually does what you expect, you can wrap it in an 'echo' call and set `subprocess: true` so that it doesn't actually execute the command but you can see how the placeholders were resolved. Alternatively you can run lazygit in debug mode with `lazygit --debug` and in another terminal window run `lazygit --logs` to see which commands are actually run
+If you want to verify that your command actually does what you expect, you can wrap it in an 'echo' call and set `showOutput: true` so that it doesn't actually execute the command but you can see how the placeholders were resolved. Alternatively you can run lazygit in debug mode with `lazygit --debug` and in another terminal window run `lazygit --logs` to see which commands are actually run
### More Examples