Merge branch 'master' into next

[i3/i3] / docs / hacking-howto

diff --git a/docs/hacking-howto b/docs/hacking-howto
index 1d2d608d12c1a6bce335518df8e032cfba4390c2..73ae96335991d5312e1b61b5a0c265be8a16926f 100644 (file)
--- a/docs/hacking-howto
+++ b/docs/hacking-howto
@@ -683,7 +683,8 @@ all commands.
 
 In earlier versions of i3, interpreting these commands was done using lex and
 yacc, but experience has shown that lex and yacc are not well suited for our
-command language. Therefore, starting from version 4.2, we use a custom parser.
+command language. Therefore, starting from version 4.2, we use a custom parser
+for user commands (not yet for the configuration file).
 The input specification for this parser can be found in the file
 +parser-specs/commands.spec+. Should you happen to use Vim as an editor, use
 :source parser-specs/highlighting.vim to get syntax highlighting for this file
@@ -935,6 +936,11 @@ Without much ado, here is the list of cases which need to be considered:
   leads to code which looks like it works fine but which does not work under
   certain conditions.
 
+* Forgetting to call `floating_fix_coordinates(con, old_rect, new_rect)` after
+  moving workspaces across outputs. Coordinates for floating containers are
+  not relative to workspace boundaries, so you must correct their coordinates
+  or those containers will show up in the wrong workspace or not at all.
+
 == Using git / sending patches
 
 For a short introduction into using git, see