r/i3wm • • Nov 01 '22

PSA: i3-gaps has been merged into i3

988 Upvotes

Today is a monumental day for me -- by far the most commonly asked questions in my ~8 years of maintaining i3-gaps has been: "Why don't you merge it into i3?". Well, today is the day this question can finally come to an end.

What's happening?

As of today, we have merged all i3-gaps features into i3 (pull request). Except for minor technical differences, users will be able to switch to i3 with their i3-gaps config seamlessly.

Note that we decided to merge i3-gaps more or less "as-is". This means all the existing restrictions and issues will remain for the time being, but the major benefit here is that we got to just finally do it (after many years).

If you have any questions, I'll do my best to answer them.

What's next?

For now, the change has been merged, but not yet released (it will be i3 4.22). As some (but not many) changes were made, it would be appreciated if people could give the current i3 HEAD a try to make sure things are working as before.

What does this mean for i3-gaps?

I will archive the project on GitHub and redirect to i3 instead. The repository will remain, however. Any issues worth keeping will be migrated to i3.

Once i3 4.22 is released, distros can simply replace any i3-gaps package with the i3 one, and everything should happen automatically for users.

What does this mean for me?

For me this is the end of an almost decade-long journey with i3-gaps. It started in r/unixporn, and it led me to become a maintainer for i3. i3 and i3-gaps have had a big impact on my life, private and professional, good and bad. So a "thank you" to everyone along the way, from Michael, TonyC and Orestis (maintainers) to all the people in the community and just everyone who enjoys using i3.


r/i3wm • • Apr 27 '20

OC Are memes allowed?

Post image
935 Upvotes

r/i3wm • • Dec 21 '20

OC I love the freedom I have to leave my laptop open knowing that no one in my family knows how to use dmenu 😁

Post image
580 Upvotes

r/i3wm • • Oct 13 '20

OC Finally I switched

Post image
569 Upvotes

r/i3wm • • Mar 19 '20

OC TIL: DuckDuckGo has i3 keybindings cheatsheet

Post image
495 Upvotes

r/i3wm • • Jun 17 '19

OC We may finally bring gaps into i3

492 Upvotes

Hello everyone,

during a discussion around packaging i3-gaps for Debian (thanks everyone involved in this!) Michael, the owner of i3, has reconsidered bringing gaps into i3 itself given the overwhelming demand the fork has.

This includes not just gaps, but all other features offered by i3-gaps as well, and probably the non-gaps related features may simply be ported in the near future.

However, for the core feature "gaps" this isn't quite as easy as porting as the implementation of gaps is currently more of a workaround as my goal has been to keep the patch simple so i3-gaps can stay up to date with upstream. For bringing gaps into i3, we'd have to do this "properly". I thought many of you might be interested in this topic, so you can find the issue here:

https://github.com/i3/i3/issues/3724

If anyone would like to support this, please give the issue an upvote (but please no +1 comments). If you would like to help by testing a change should we get a PR going, please subscribe to the issue to stay informed. If you would like to help by discussing the strategy or even contributing code yourself, join us on GitHub. :-)


r/i3wm • • Sep 30 '20

OC I bet being able to visualise your config file changes is a great skill...

Post image
463 Upvotes

r/i3wm • • 8d ago

OC Rate my i3 rice

Post image
410 Upvotes

r/i3wm • • Sep 26 '20

Posting here cos unixporn removed my submission and I don't have any friends to show it off. pls don't hate me.

Post image
401 Upvotes

r/i3wm • • Dec 30 '20

An update on the future of i3

387 Upvotes

Hello everyone,

we, that is the core contributors to i3, have recently internally discussed how we want to handle feature requests for i3 in the future. As you probably know, i3 has been fairly conservative with new features already, dating back at least as far as I have been a part of this project. This means it is to no surprise that we actually feel that i3 is in a pretty good spot in terms of features at this point. In the "recent" past we've often rejected new feature requests because of this unspoken feeling. If this is how we maintain the project, however, it's only fair that we publicly state our feelings regarding new features upfront.

Therefore, we have decided to take an official stance that we're happy with the feature set of i3, and that new features will generally only be considered if they can either be implemented without further configuration/commands (and without being a breaking change, of course), or if they are so fundamentally beneficial that they outweigh the cost they add to the project. To set expectations, however, we don't really expect the latter point to happen very often anymore. Instead, we want to focus the development on stability and maintenance, i.e. fixing bugs and the like. A lot of the feature requests we get can actually also be implemented outside of i3, for example using the IPC, and whenever this is possible, we will recommend that this is the approach users take.

We have updated our GitHub issue templates as well as added a new project goal on the i3wm homepage:

Do not add further complexity when it can be avoided. We are generally happy with the feature set of i3 and instead focus on fixing bugs and maintaining it for stability. New features will therefore only be considered if the benefit clearly outweighs the additional complexity, and we encourage users to implement features using the IPC whenever possible.

Questions?

Of course we anticipate that this may raise some questions in the community, so please feel free to discuss them with us here, on the mailing list or in the form of issues on GitHub. I'll try to answer some questions which I expect to come up:

Why are you doing this? What's wrong with optional features?

This is probably the kind of question we get the most whenever a feature is rejected, so I'd like to answer this here as well.

More features come with more configuration, documentation, and "logical branches". This contributes complexity into the system, and complexity can lead to instability. It's never "the one feature" that is problematic, but rather the sum of them all. The simple truth is also that while new features are often contributed by the community, the maintenance work for that virtually always ends up being the core team's job, further making the point on why "just make it a flag" just isn't a good approach (for us).

Does this mean i3 is dead?

No. We essentially continue as-is, but we're more open about our expectations regarding feature requests.

What does this mean for the integration of i3-gaps?

We haven't specifically discussed this, but as the maintainer of i3-gaps I would probably say that you should not get your hopes up. I could still see us accepting this should someone rise up to the challenge, but objectively it's not very likely that this will happen. I also feel that while that would be nice-to-have, there's no real issue with the way things currently are.

What about sway?

First off, we're in no way involved with the sway team. However, this discussion was actually semi-sparked by the fact that feature requests have been raised against i3 by sway users, simply because sway is feature-frozen and only implements features also implemented by i3 at this point.

This is entirely a project decision on the sway side, and we discussed whether we want to take such a strong "no more features" stance as well. However, we decided that we'd like to at least be open to new ideas still, and if they're convincing enough there's no reason they cannot be implemented. We simply want to set the bar for that high.


r/i3wm • • Feb 22 '22

OC Thank you i3 that I don't have to live like this any more.

Post image
353 Upvotes

r/i3wm • • 17d ago

Solved Keep it simple

Post image
350 Upvotes

r/i3wm • • Jul 28 '20

OC Wrote a Native Tiling Window Manager similar to i3 in windows 10 in C (Win32 Code only)

Post image
350 Upvotes

r/i3wm • • Dec 29 '25

OC i3 is the best

Post image
328 Upvotes

with pywal so it changes with the wallpaper, it's my daily drive that I use for study, coding and literally everything

I forgot to upload the dots sorry 😅


r/i3wm • • Jun 27 '20

OC dmenu-rs now has a built in calculator, one that is more feature rich than every alternative. Plus, it's written in Rust.

312 Upvotes

r/i3wm • • May 26 '21

OC I bet being able to visualise your config file changes is a great skill...

Post image
305 Upvotes

r/i3wm • • Jan 19 '20

OC Need to focus? Try i3-quiet mode!

Post image
299 Upvotes

r/i3wm • • Mar 22 '20

OC Matrix lock screen

279 Upvotes

r/i3wm • • Jan 29 '26 WOW

OC I have made my i3 useful like any desktop environment also keep the i3 keybind for the advantage

275 Upvotes

the challenge is sometimes many qt and gtk apps theme are hardcoded so I have to find the file so I can match my color scheme, overall I just use qt6ct and xsettingsd for gtk


r/i3wm • • May 28 '21

OC My first fully functional i3 and Polybar workspace

Post image
267 Upvotes

r/i3wm • • Jun 09 '22

OC This is the way

Post image
262 Upvotes

r/i3wm • • Oct 17 '19

Question Workspace 15032385536 doesn't follow order

262 Upvotes

I tend to use a lot of workspaces, and this is a really glaring obvious big annoying problem to me. Take a look:

Workspaces 0 to 15032385535 behave fine, but by the time I have to do something more serious, I tend to need more workspaces than that. And, when I reach workspace 15032385536, the ordering breaks, as if these numbers turn "negative" or something. This is really hindering my workflow on a daily basis and I could really use to have it fixed.


r/i3wm • • May 04 '18

OC Using i3 for better accessibility with Parkinson's Disease

261 Upvotes

About a month ago, /u/EllaTheCat mentioned in a post that they use i3 not despite, but also because they have Parkinson's Disease (PD). We typically think of i3 as a tool for power users to make things more efficient, so to think of using i3 as a way of dealing with something like PD was both surprising and intriguing to me. I asked /u/EllaTheCat to write a small article about how exactly this works, and they were kind enough to do so.

You can find the repository with the write-up as well as configs and scripts here:

https://github.com/EllaTheCat/i3-parkinson

For me, it is really cool to see this and I'd really like to thank /u/EllaTheCat for agreeing to write this article from which there are definitely things to learn. I hope that the community can find it even half as interesting as it has been for me!


r/i3wm • • Jan 12 '22

OC i3wm [3860x2140] Made for the community, hope you like it.

Post image
256 Upvotes