From: Franz Thoma <franz.thoma@tngtech.com>
Date: Mon, 28 Dec 2015 18:38:17 +0000 (+0100)
Subject: Comply with documentation: 'workspace' token in 'assign' command
X-Git-Tag: 4.12~77^2
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=refs%2Fpull%2F2137%2Fhead;p=i3%2Fi3

Comply with documentation: 'workspace' token in 'assign' command

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
---

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)