i3
dwm
Our great sponsors
i3 | dwm | |
---|---|---|
200 | 22 | |
9,053 | 0 | |
1.7% | - | |
7.6 | 6.8 | |
5 days ago | 4 months ago | |
C | C | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
i3
-
Show HN: Chrome Reaper
While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:
https://github.com/i3/i3/issues/4353
-
Firefox 121 defaults to Wayland on Linux
> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).
Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393
It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."
It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.
But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.
The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.
-
"We understand" ;)
This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.
-
what machines have you used for development, and what do you prefer?
I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development.
-
The future of /r/i3wm
Even though, we have moved the official i3 support channel to GitHub discussions, i3's biggest community is still on reddit and if things continue like that there is going to be a lot of helpful content on an increasingly closed platform.
- while in i3wm, krita dockers move downwards a bit each time they're spawned - how do I fix this?
- i3wm-like window switching for Windows
-
egui_overlay - A transparent Overlay window where you can only click the "egui parts"
for example, take i3. https://github.com/i3/i3/issues/4478
- How to start on a Linux desktop environment?
-
Machine for pentesting and general use?
For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it
dwm
-
Major improvement in wrist fatigue?
I switched to Vim a little above a year ago. It is a keyboard-driven text editor. You can't open it and just start typing like notepad, you open it then you have to press a command to start typing—i or a are the most simple. When you are done typing, you press escape to leave insert ("text-editing") mode and go back into visual ("navigation") mode. You then write changes and close the editor with ZZ. Now, a few months before I started using my new keyboard, I started using a tiling Window Manager—dwm—which allowed me to do most of my window management and navigation with the keyboard alone.
-
Using Arch Linux
Now I had to get a “GUI” up and running. I had used KDE and GNOME on my old laptop before but I wanted to try something called a tiling window manager. If you didn’t know, tiling window managers basically automatically resize windows based on available space, so instead of having a bunch of windows overlapping each other like macOS or Windows, all of them are on the screen and visible to the user. For this, I was going to use a tiling window manager called dwm .
-
Moving between workspaces
I'm coming from https://dwm.suckless.org/ so I am very confused by the MacOS window manager. I know I can Control+{1..9} to move between Desktop workspaces, but that stops working if I full screen an Application? So how do people quickly move between a terminal and a certain browser profile? Bonus: How do remove that slow transition animation?
-
[OC] Dynamic tiling (master-stack) proof of concept script for sway
To see properly implemented dynamic master-stack tiling, see the x window manager dwm or the wayland compositor river.
-
Wayland or X11 programming for beginners ?
You can also check out DWM (X11) written in 2000 SLOC, so should be easy to understand.
-
A window manager that doesn't require you to edit the source code for basic customization? Heresy! (googles how to open window in dwm)
People should be scared of editing source code. That keeps Noobs and people with jobs away
-
Update. If installed arch successfully with the German version of arch wiki.
Tiling wm with stack layout (from suckless) https://dwm.suckless.org
-
desktop window manager
dynamic window manager = tiling window manager by suckless, https://dwm.suckless.org
-
What's the use of having multiple Desktops? Have never used it myself..wanted to know what people use it for..
I work mostly with full screen windows, or Monocle mode as dwm and the like call it. The trackpad makes it very easy to swipe between spaces and I keep things in a defined order so no matter what app I'm currently using I can quickly get to any other app.
- Suckless so called Philosophy
What are some alternatives?
sway - i3-compatible Wayland compositor
void-packages - The Void source packages collection
awesome - awesome window manager
libxft-bgra - A patched version of libxft that allows for colored emojis to be rendered in Suckless software (dmenu/st/whatever).
bspwm - A tiling window manager based on binary space partitioning
yabai - A tiling window manager for macOS based on binary space partitioning
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
conky - Light-weight system monitor for X, Wayland (sort of), and other things, too
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager
velox - velox window manager
tmux - tmux source code
river - [mirror] A dynamic tiling Wayland compositor