Originally created by @Inqurity on GitHub (Sep 17, 2023).
Describe the bug
Pressing the window resize shortcut or using the resize-axis command don't change the window size in any workspace except workspace 0, nor do they output an error
To Reproduce
Steps to reproduce the behavior:
Move two or more windows to a separate workspace
Try resizing them
Expected behavior
A change in window size, like it is in workspace 0
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.22621 N/A Build 22621
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
BIOS Version: American Megatrends International, LLC. FX506HF.307, 7/20/2023
komorebic check Output
Provide the output of komorebic check
For example:
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\alexa
Looking for configuration files in C:\Users\alexa
No komorebi configuration found in C:\Users\alexa
If running 'komorebic start --await-configuration', you will manually have to call the following command to begin tiling: komorebic complete-configuration
Additional context
I am not sure if this is an issue on komorebi end, as this is such a popular and quality project, sorry if i did something wrong
Originally created by @Inqurity on GitHub (Sep 17, 2023).
**Describe the bug**
Pressing the window resize shortcut or using the resize-axis command don't change the window size in any workspace except workspace 0, nor do they output an error
**To Reproduce**
Steps to reproduce the behavior:
1. Move two or more windows to a separate workspace
2. Try resizing them
**Expected behavior**
A change in window size, like it is in workspace 0
**Screenshots and Videos**
https://github.com/LGUG2Z/komorebi/assets/65112064/f75a9f71-de05-4811-8240-9b08fb154299
**Operating System**
```
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.22621 N/A Build 22621
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
BIOS Version: American Megatrends International, LLC. FX506HF.307, 7/20/2023
```
**`komorebic check` Output**
Provide the output of `komorebic check`
For example:
```
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\alexa
Looking for configuration files in C:\Users\alexa
No komorebi configuration found in C:\Users\alexa
If running 'komorebic start --await-configuration', you will manually have to call the following command to begin tiling: komorebic complete-configuration
```
**Additional context**
I am not sure if this is an issue on komorebi end, as this is such a popular and quality project, sorry if i did something wrong
adam
added the bug label 2026-01-05 14:49:14 +01:00
The resize command only works for the BSP layout, or for the primary column in custom layouts. If your other workspaces have layouts besides BSP or custom, then this is the expected behaviour.
@LGUG2Z commented on GitHub (Sep 17, 2023):
The resize command only works for the BSP layout, or for the primary column in custom layouts. If your other workspaces have layouts besides BSP or custom, then this is the expected behaviour.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Inqurity on GitHub (Sep 17, 2023).
Describe the bug
Pressing the window resize shortcut or using the resize-axis command don't change the window size in any workspace except workspace 0, nor do they output an error
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A change in window size, like it is in workspace 0
Screenshots and Videos
https://github.com/LGUG2Z/komorebi/assets/65112064/f75a9f71-de05-4811-8240-9b08fb154299
Operating System
komorebic checkOutputProvide the output of
komorebic checkFor example:
Additional context
I am not sure if this is an issue on komorebi end, as this is such a popular and quality project, sorry if i did something wrong
@LGUG2Z commented on GitHub (Sep 17, 2023):
The resize command only works for the BSP layout, or for the primary column in custom layouts. If your other workspaces have layouts besides BSP or custom, then this is the expected behaviour.