gaps

[rainerborene]

I know this was already discussed somewhere else but why do you hesitate to merge gaps to the codebase? Even If it's i3 philosophy to use all space on screen I think it is up to the user decide that on his/her own configuration file. More and more users are moving from i3 to bspwm or any other wm with gaps feature. Please consider the use case of users using large monitors, which makes sense using gaps. If you really dislike gaps it should be disabled by default.

[i3bot]

I don’t see a link to logs.i3wm.org. Did you follow http://i3wm.org/docs/debugging.html? (In case you actually provided a link to a logfile, please ignore me.)

[i3bot]

I don’t see a version number. Could you please copy & paste the output of i3 --version into this issue?

[okraits]

There's a fork of i3 with gaps: https://github.com/Airblader/i3

I think the reason for not implementing gaps is that it has no practical value and that it adds complexity and possibilities for bugs to the codebase.

I don't see why you would need gaps to be able to use large monitors :)
And i don't see masses of users moving away from i3 because of gaps either :)

[stapelberg]

Even If it's i3 philosophy to use all space on screen I think it is up to the user decide that on his/her own configuration file.

I respectfully disagree. See https://faq.i3wm.org/question/778/why-is-patch-not-merged-and-made-optional/ for the reasoning.

More and more users are moving from i3 to bspwm or any other wm with gaps feature.

I couldn’t care less. The old “people will not use your software anymore if you don’t implement $x” argument doesn’t work on me/us :).

If people won’t use i3 because of gaps, perhaps they actually are better off with some other window manager that emphasizes the visual appearence more.