i3
kinto
Our great sponsors
i3 | kinto | |
---|---|---|
200 | 132 | |
9,053 | 4,097 | |
1.7% | - | |
7.6 | 3.2 | |
5 days ago | about 1 month ago | |
C | Python | |
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 only |
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
kinto
- RavynOS Finesse of macOS. Freedom of FreeBSD
-
Learn AutoHotKey by stealing my scripts
If you like macOS keyboard shortcuts, I recommend you checkout Kinto go Windows and Linux. On Windows, Kinto used AHK
https://kinto.sh
However, at least when I set it up Kinto did not provide switching windows I’m this fashion. Here is the script I use.
```
; BRING FORWARD ALL WINDOWS OF THE CURRENT APPLICATION
-
Toshy v23.08: Mac-like per-app keyboard shortcuts. Now supports Solus 4.4.
The project was based on another project that's been around for a few years called Kinto, by Ben Reaves, which notably also has a Windows version (https://kinto.sh) using AutoHotkey. But has no Wayland support (at this time) in its Linux version.
-
Toshy v23.07: Mac-like per-app keyboard shortcuts. Supports Tumbleweed and Leap.
Toshy is based on Kinto.sh, by Ben Reaves (https://kinto.sh or https://github.com/rbreaves/kinto). Kinto is basically an extensive keymapper config that not only shifts modifier keys appropriately for different keyboard types, but has full keymaps for a number of different apps like VSCode. My variant of Kinto adds some features and utilities for managing the services that make it work, and tools like a script to change the function keys mode of any keyboard that uses hid_apple. That means MacBook keyboards mostly, but also some non-Apple keyboards with media keys apparently use that driver module.
- Toshy v23.07: Mac-like per-app keyboard shortcuts on KDE (supports Wayland+KDE)
-
Swap alt and win keys using command line
I don’t know if you can activate it via a keyboard shortcut, but I use Kinto.sh to swap keys on my MacBooks.
-
Macbook keyboard type for Fedora
Hello, there's an open issue about this in their repo: https://github.com/rbreaves/kinto/issues/772
-
emergency mac user,can i make it more linux?
There is a setting in keyboard preferences for that.However if you can get yourself used to macOS shortcuts I highly recommend doing so as they seem to be superior especially if you are a programmer and use the terminal a lot, as on macOS you can simply use Command+C to copy from a terminal and Ctrl+C still works for sending SIGINT. Also Command+, will open preferences for almost every application on macOS. Shortcuts on macOS are very consistent across many apps unlike on Linux or Windows. After you get your Linux laptop back you can continue using these shortcuts thanks to a tool called kinto.sh.
-
Keyd: Linux Key Remapper
Tangential: I'm currently looking for a way to map Mac-style shortcuts on Linux (e. g. Meta + C/V for copy / paste). The only thing I know is https://kinto.sh/, but it looks a bit too janky to my taste. Any other ideas?
-
Reviving an old MacBook with Linux? Do these immediately.
And nothing about installing my https://kinto.sh app?
What are some alternatives?
sway - i3-compatible Wayland compositor
autohotkey-windows-mac-keyboard - AutoHotkey Mappings to emulate OSX behaviour with a Mac keyboard on Windows
awesome - awesome window manager
touchegg - Linux multi-touch gesture recognizer
bspwm - A tiling window manager based on binary space partitioning
keyd - A key remapping daemon for linux.
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
AutoKey - AutoKey, a desktop automation utility for Linux and X11.
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager
Unshaky - A software attempt to address the "double key press" issue on Apple's butterfly keyboard [not actively maintained]
tmux - tmux source code
espanso - Cross-platform Text Expander written in Rust