From f57300c9f50b42f87aa53b69952cce5337693ed7 Mon Sep 17 00:00:00 2001 From: Mark Phillipson Date: Wed, 25 Mar 2026 16:40:18 +0000 Subject: [PATCH 1/2] Fix link format for tags in modes.md Updated link format for tags in modes.md to ensure proper hyperlinking. The existing link did not work. --- docs/Customization/Talon Framework/modes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Customization/Talon Framework/modes.md b/docs/Customization/Talon Framework/modes.md index ee8cc4b1..e8a5a5b2 100644 --- a/docs/Customization/Talon Framework/modes.md +++ b/docs/Customization/Talon Framework/modes.md @@ -17,7 +17,7 @@ mode: dictation insert mode: "dictation mode active" ``` -You can create custom modes but this is uncommon as [tags](tags) are better suited for most purposes. Like tags, multiple modes can be active at once. Unlike Tags, modes cannot be scoped to a particular context; modes always apply globally. The intent is that there should be a small enough number of them that they could be toggled using a short popup menu. +You can create custom modes but this is uncommon as [tags](https://talon.wiki/Customization/Talon%20Framework/tags) are better suited for most purposes. Like tags, multiple modes can be active at once. Unlike Tags, modes cannot be scoped to a particular context; modes always apply globally. The intent is that there should be a small enough number of them that they could be toggled using a short popup menu. So why might you add a custom mode? The main reason is because you want to disable all normal voice commands so only the ones in your mode are active. An example might be where you were using a full screen computer game, and wanted to eliminate potential conflicts with commands outside the game context. From 12fe8b61b4b320300796a5410e01ad856949dddb Mon Sep 17 00:00:00 2001 From: Mark Phillipson Date: Fri, 27 Mar 2026 11:06:32 +0000 Subject: [PATCH 2/2] Update docs/Customization/Talon Framework/modes.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/Customization/Talon Framework/modes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Customization/Talon Framework/modes.md b/docs/Customization/Talon Framework/modes.md index e8a5a5b2..dafaa955 100644 --- a/docs/Customization/Talon Framework/modes.md +++ b/docs/Customization/Talon Framework/modes.md @@ -17,7 +17,7 @@ mode: dictation insert mode: "dictation mode active" ``` -You can create custom modes but this is uncommon as [tags](https://talon.wiki/Customization/Talon%20Framework/tags) are better suited for most purposes. Like tags, multiple modes can be active at once. Unlike Tags, modes cannot be scoped to a particular context; modes always apply globally. The intent is that there should be a small enough number of them that they could be toggled using a short popup menu. +You can create custom modes but this is uncommon as [tags](./tags.md) are better suited for most purposes. Like tags, multiple modes can be active at once. Unlike Tags, modes cannot be scoped to a particular context; modes always apply globally. The intent is that there should be a small enough number of them that they could be toggled using a short popup menu. So why might you add a custom mode? The main reason is because you want to disable all normal voice commands so only the ones in your mode are active. An example might be where you were using a full screen computer game, and wanted to eliminate potential conflicts with commands outside the game context.