rofi
i3
Our great sponsors
rofi | i3 | |
---|---|---|
152 | 200 | |
12,404 | 9,053 | |
1.9% | 1.7% | |
8.6 | 7.6 | |
8 days ago | 4 days ago | |
C | C | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" 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.
rofi
- Rofi: A window switcher, application launcher and dmenu replacement
- macOS Command-Line Tools You Might Not Know About
-
What is the appeal of the 'start menu' in so many desktop environments?
You'll probably like rofi.
-
Possible to filter clipboard when using `unamedplus`?
Also, I use this script so that Rofi will show my clipboard instead of the native klipper UI (because it's far less keyboard friendly). Normally the script works great, but the script chokes whenever I `dd` an empty line or a lone `\`, putting an empty entry on my clipboard, which the wrapper than assumes means I'm at the end of the list of clipboard entries.
-
Rofi dry run
Which rofi you run? The original one from https://github.com/davatorium/rofi (which is Xorg base, so it has to start XWayland) or the Wayland-based fork on https://github.com/lbonn/rofi?
-
Cozytile - A Cozy Qtile Rice
OS: Arch Linux WM: Qtile Panel: Qtile bar Launcher: Rofi Notification Daemon: Dunst Terminal: Alacritty Shell: Zsh Compositor: Picom File Manager: Nemo Music Player: Spotify & ncmpcpp
- [Manjaro Linux] Manjaro + XFCE + ROFI + DRACULA THÈME
-
What's your recommended launcher app in your opinion?
I like rofi (super flexible, i also use it as a custom alt-tab option in openbox) and wofi is a nice option on wayland
-
xfce workplace switcher in polybar
Modi are covered in the documentation. They set what Rofi displays in its window. You can run Rofi from a keybind, or a module in Polybar, or by using click handlers. Extremely extensible and versatile. And a shit ton of fun to theme. :)
-
A sensible NixOS Xfce desktop configuration
xwinmosaic: Having tried XMonad.Actions.GridSelect in the past, I found the 2-dimensional grid more confusing than useful because you cannot intuit where it would lay things out. I find Rofi to be more usable for window switching because it prioritizes text filtering. https://github.com/davatorium/rofi
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
What are some alternatives?
albert - A fast and flexible keyboard launcher
sway - i3-compatible Wayland compositor
dmenu-rs - A pixel perfect port of dmenu, rewritten in Rust with extensive plugin support
awesome - awesome window manager
polybar - A fast and easy-to-use status bar
bspwm - A tiling window manager based on binary space partitioning
Ulauncher - Feature rich application Launcher for Linux
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
nerd-fonts - Iconic font aggregator, collection, & patcher. 3,600+ icons, 50+ patched fonts: Hack, Source Code Pro, more. Glyph collections: Font Awesome, Material Design Icons, Octicons, & more
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager
dunst - Lightweight and customizable notification daemon
tmux - tmux source code