From ee66a8bcde5adc0890b5a8d02705c48dfa1b7cb5 Mon Sep 17 00:00:00 2001 From: Michael Stapelberg Date: Sun, 3 May 2015 18:57:05 +0200 Subject: [PATCH] =?utf8?q?userguide:=20quoted=20strings=20need=20to=20be?= =?utf8?q?=20used,=20escaping=20isn=E2=80=99t=20possible?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit fixes #1678 --- docs/userguide | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/userguide b/docs/userguide index 80de5c88..820f5395 100644 --- a/docs/userguide +++ b/docs/userguide @@ -699,6 +699,10 @@ commands will not run when restarting i3, if you need a command to run also when restarting i3 you should use the +exec_always+ keyword. These commands will be run in order. +See <> for details on the special meaning of +;+ (semicolon) +and +,+ (comma): they chain commands together in i3, so you need to use quoted +strings if they appear in your command. + *Syntax*: ------------------- exec [--no-startup-id] command @@ -1466,7 +1470,11 @@ information on how to use them. What good is a window manager if you can’t actually start any applications? The exec command starts an application by passing the command you specify to a shell. This implies that you can use globbing (wildcards) and programs will be -searched in your $PATH. +searched in your +$PATH+. + +See <> for details on the special meaning of +;+ (semicolon) +and +,+ (comma): they chain commands together in i3, so you need to use quoted +strings if they appear in your command. *Syntax*: ------------------------------ -- 2.39.5