From e7e2ed94fd173dc9bef3d60cf0d5fbc593136e1e Mon Sep 17 00:00:00 2001 From: Miguel de Val-Borro Date: Fri, 23 Dec 2011 12:56:26 +0100 Subject: [PATCH 1/3] Fix typo in keyboard binding example in the user guide --- docs/userguide | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/userguide b/docs/userguide index be8335ef..05c15229 100644 --- a/docs/userguide +++ b/docs/userguide @@ -323,7 +323,7 @@ bindcode [Modifiers+]keycode command *Examples*: -------------------------------- # Fullscreen -bindsym mod+f f +bindsym mod+f fullscreen # Restart bindsym mod+Shift+r restart From 538247a8431059ea3b97c41e20a2efb3f1cef257 Mon Sep 17 00:00:00 2001 From: Michael Stapelberg Date: Sat, 24 Dec 2011 15:36:11 +0100 Subject: [PATCH 2/3] s/xwininfo/xprop (Thanks Miguel) --- docs/userguide | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/userguide b/docs/userguide index 05c15229..4bae0406 100644 --- a/docs/userguide +++ b/docs/userguide @@ -519,7 +519,7 @@ use it, it has to be a UTF-8 encoded arrow, not `->` or something like that. To get the class and instance, you can use +xprop+. After clicking on the window, you will see the following output: -*xwininfo*: +*xprop*: ----------------------------------- WM_CLASS(STRING) = "irssi", "URxvt" ----------------------------------- From 1d2c63de5cb022a2381d7d4f492e5be855d090ac Mon Sep 17 00:00:00 2001 From: Miguel de Val-Borro Date: Fri, 23 Dec 2011 16:29:26 +0100 Subject: [PATCH 3/3] Fix a few spelling typos --- docs/userguide | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/userguide b/docs/userguide index 4bae0406..e75f1ca1 100644 --- a/docs/userguide +++ b/docs/userguide @@ -174,7 +174,7 @@ Floating windows are always on top of tiling windows. i3 stores all information about the X11 outputs, workspaces and layout of the windows on them in a tree. The root node is the X11 root window, followed by the X11 outputs, then dock areas and a content container, then workspaces and -finally the windows themselve. In previous versions of i3 we had multiple lists +finally the windows themselves. In previous versions of i3 we had multiple lists (of outputs, workspaces) and a table for each workspace. That approach turned out to be complicated to use (snapping), understand and implement. @@ -619,7 +619,7 @@ Only clients that do not cover the whole area of this window expose the color used to paint it. If you use a color other than black for your terminals, you most likely want to set the client background color to the same color as your terminal program's background color to avoid black gaps between the rendered -area of the termianal and the i3 border. +area of the terminal and the i3 border. Colors are in HTML hex format (#rrggbb), see the following example: @@ -1185,7 +1185,7 @@ number or name of the workspace. To move containers to specific workspaces, use You can also switch to the next and previous workspace with the commands +workspace next+ and +workspace prev+, which is handy, for example, if you have workspace 1, 3, 4 and 9 and you want to cycle through them with a single key -combination. Similarily, you can use +move workspace next+ and +move workspace +combination. Similarly, you can use +move workspace next+ and +move workspace prev+ to move a container to the next/previous workspace. [[back_and_forth]] @@ -1195,7 +1195,7 @@ back_and_forth+. To move a container to another xrandr output such as +LVDS1+ or +VGA1+, you can use the +move output+ command followed by the name of the target output. You may also use +left+, +right+, +up+, +down+ instead of the xrandr output name to -move to the the next output in the specified direction. +move to the next output in the specified direction. *Examples*: -------------------------