From c3353bb27317d294a91a8accec9a554ea392de04 Mon Sep 17 00:00:00 2001
From: Jason <ammgws@users.noreply.github.com>
Date: Mon, 6 Jan 2020 16:42:56 +0900
Subject: Docs: explain why menu command should be passed to sway

It was not obvious to me why until I saw a comment from @RyanDwyer on Reddit, so I think it's better to add an explanation.
---
 config.in | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'config.in')

diff --git a/config.in b/config.in
index 17d8c9f3..67c748ba 100644
--- a/config.in
+++ b/config.in
@@ -16,7 +16,8 @@ set $right l
 # Your preferred terminal emulator
 set $term alacritty
 # Your preferred application launcher
-# Note: it's recommended that you pass the final command to sway
+# Note: pass the final command to swaymsg so that the resulting window can be opened
+# on the original workspace that the command was run on.
 set $menu dmenu_path | dmenu | xargs swaymsg exec --
 
 ### Output configuration
-- 
cgit v1.2.3-54-g00ecf