i3/RELEASE-NOTES-next


 ┌──────────────────────────────┐
 │ Release notes for i3 v4.20   │
 └──────────────────────────────┘

This is i3 v4.19. This version is considered stable. All users of i3 are
strongly encouraged to upgrade.


 ┌────────────────────────────┐
 │ Changes in i3 v4.20        │
 └────────────────────────────┘

  • i3-nagbar: position on focused monitor by default
  • i3-nagbar: add option to position on primary monitor
  • alternate focusing tab/stack children-parent containers by clicking on their titlebars

 ┌────────────────────────────┐
 │ Bugfixes                   │
 └────────────────────────────┘

  • when initializing new outputs, avoid duplicating workspace numbers
  • fix workspaces not moving to assigned output after output becomes available
release.sh and release notes changes post-release (#4258) 2020-11-15 19:22:09 +01:00
			`┌──────────────────────────────┐`
			`│ Release notes for i3 v4.20 │`
			`└──────────────────────────────┘`

			`This is i3 v4.19. This version is considered stable. All users of i3 are`
			`strongly encouraged to upgrade.`


			`┌────────────────────────────┐`
			`│ Changes in i3 v4.20 │`
			`└────────────────────────────┘`

i3-nagbar: add possibility to open bar on focused monitor Closes #3692 i3-nagbar will open by default on the monitor with input focus and using the flag -p on the primary monitor. 2020-11-02 22:16:48 +02:00			`• i3-nagbar: position on focused monitor by default`
			`• i3-nagbar: add option to position on primary monitor`
Implement context-sensitive tab-clicking behavior This commit makes it so that when clicking on a tab for the first time, its inactive-focused child is focused. This matches i3 behavior when scrolling on tabs. A second click on the tab titlebar focuses the tab container itself. Subsequent clicks cycle between these two states. Closes #4225. 2020-10-25 22:20:25 -04:00			`• alternate focusing tab/stack children-parent containers by clicking on their titlebars`
release.sh and release notes changes post-release (#4258) 2020-11-15 19:22:09 +01:00
			`┌────────────────────────────┐`
			`│ Bugfixes │`
			`└────────────────────────────┘`

create_workspace_on_output: Prevent duplicate workspace nums When going through the `binding_workspace_names` to prioritize user-specified names, we only check if the workspace exists, not the workspace number. If the user specified a `bindsym … workspace number X` directive, then it is appended in `binding_workspace_names` and a workspace is created using that number even though from the POV of a user that uses numbers to change workspaces, that workspace already exists. In similar code here: https://github.com/i3/i3/blob/1d9160f2d247dbaa83fb62f02fd7041dec767fc2/src/workspace.c#L997 we do the check. Fixes #4238 2020-11-10 10:24:15 +01:00			`• when initializing new outputs, avoid duplicating workspace numbers`
Fix workspace assignements after output changes Fix #4261 The previous method was modifying the same list it was iterating upon causing an erronous iteration and thus not every workspace got assigned back to were they should (only the first one). 2020-12-29 21:45:39 +01:00			`• fix workspaces not moving to assigned output after output becomes available`