From 194da2d7cfb90ee23ad8bdce6ca3e20e2f27abc1 Mon Sep 17 00:00:00 2001 From: Franz Thoma Date: Mon, 28 Dec 2015 19:38:17 +0100 Subject: [PATCH] Comply with documentation: 'workspace' token in 'assign' command MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit According to the User's Guide [1], an `assign` command allows a `workspace` token after the selector, as an alternative or in addition to the unicode arrow `→`. In reality, however, the `workspace` token is not recognized. Example: assign [class="Firefox"] workspace "1: Browser" should assign Firefox windows to workspace `1: Browser`, but the the browser window appears on a new workspace called `workspace "1: Browser"` instead. With this fix, both `→` and `workspace` are recognized (and ignored) after the selector. [1] https://i3wm.org/docs/userguide.html#_automatically_putting_clients_on_specific_workspaces --- parser-specs/config.spec | 2 ++ 1 file changed, 2 insertions(+) diff --git a/parser-specs/config.spec b/parser-specs/config.spec index 882e81fb..9dad79c0 100644 --- a/parser-specs/config.spec +++ b/parser-specs/config.spec @@ -146,6 +146,8 @@ state ASSIGN: state ASSIGN_WORKSPACE: '→' -> + 'workspace' + -> workspace = string -> call cfg_assign($workspace) -- 2.39.2