search

Airblader / i3

A fork of the i3 window manager with gaps and some other features. :warning: i3-gaps has been merged into i3.
BSD 3-Clause "New" or "Revised" License
5.88k stars 321 forks source link

Gaps Count Towards Window Size? #396

Closed danieldugas closed 3 years ago

danieldugas commented 3 years ago

I'm submitting a…

[ ] Bug
[ ] Feature Request
[ ] Documentation Request
[x] Other (Please describe in detail)

I'm not sure whether this is a bug or intended behavior

Current Behavior

With large gaps, windows do not get tiled with equal size because gaps count towards window size: Screenshot from 2021-04-28 10-57-51

Expected Behavior

I would expect windows to get tiled with equal size despite gaps

Reproduction Instructions

bindsym $mod+g gaps horizontal all toggle 864, gaps vertical all toggle 432

open 3 windows

Environment

Output of i3 --moreversion 2>&-:

i3 version: v4.19.2
Config file

```
[default config with these lines added:]
# Specify the distance between windows in pixels. (i3-gaps)
gaps inner 10
gaps horizontal 864
gaps vertical 432
# gaps outer 0
# small mode for the big screen
bindsym $mod+g gaps horizontal all toggle 864, gaps vertical all toggle 432
```



- Linux Distribution & Version: Ubuntu 18
- Are you using a compositor (e.g., xcompmgr or compton): yes

            

        

    
            

            

                Airblader
                commented
                 3 years ago            

            

                
Thanks for posting! This is a duplicate of #22.
            

        

            

            

                orestisfl
                commented
                 3 years ago            

            

                
If this is an actual issue, shouldn't we keep it around so that it can get accounted for https://github.com/i3/i3/issues/3724?
            

        

            

            

                Airblader
                commented
                 3 years ago            

            

                
Gaps would have to be entirely reimplemented from scratch to work differently anyway, so I view this as an artifact of how i3-gaps works. If such an implementation were to produce the same effect, we'd notice it, I think.