Mouseless – keyboard-driven control of macOS/Linux/Windows(mouseless.click) |
Mouseless – keyboard-driven control of macOS/Linux/Windows(mouseless.click) |
Did anyone notice the use of the mouse at the end?
Homerow is like vimium but for your entire mac.
Like I can understand people with disabilities that makes sense so that’s not what I’m talking about
I’m talking about people who are actively choosing to be keyboard only, especially in extremely technical roles
:qa!Similar to Vimium, but for the whole OS. Apparently Homerow is similar, judging from comments I'm seeing here.
I really wish I knew an equivalent for Linux. I might even leave Gnome behind if a different DE has a good model for this.
Also, I'm not sure the dynamic nature of the hotkeys is a good thing. I could imagine if you use Mouseless for a long period of time, muscle memory might prevail as screen locations map to the same set of keys.
"Manipulate macOS masterfully, minus the mouse."
I've been looking for something like this
Wayland port: https://github.com/kovetskiy/waynav
Now, third party software, is always going to be all over the place. Stuff that was largely built on Win32 components works fine, but "modern" stylized applications rarely have strong support.
There is one major improvement you can do on Mac, at least for menus:
The problem is that they are less discoverable and you need to make and effort to get used to using them instead of point and click.
Agreed. Using keyboard keys to emulate a mouse cursor seems like it ought to be a last resort for graphical applications that lack proper accessibility affordances.
Contrast that with command palettes, accessibility controls, syntax tree navigation, and other approaches that rely on the names, content, and document structure that users already know rather than a special mode that displays two letter codes that must be read each time or memorized. Many of these other approaches also allow users to activate buttons, menu items, and links that are outside the current viewport or hidden in menus which reduces the overall number of "clicks" required to perform those actions. The downside is that they can take longer to type than a two-letter code. Still, my guess is that for most people it would be overall more efficient to optimize for cognitive load than pure speed.
(Though in the long run, I suspect that improvements in eye-tracking will lead to hybrid systems that are both lower cognitive load and faster than any of these.)
Been using this for years.
That's called mob rule. We don't act like cavemen anymore. We build entire civilizations to prevent that sort of thing. You may have read in a history book once "We hold these truths to be self-evident, that all men are created equal."
The word "all" is important.
There's plenty of TUIs for the dozens of you to use.
For vim, there's easymotion or hop.nvim.
For tmux, there's Morantron/tmux-fingers.
For Chrome, there's Vimium.
You can also flash your keyboard to have mouse controls (https://docs.qmk.fm/features/mouse_keys).
I've been using a "hamster" for some time now. Its top surface is a track pad - nice.
I was always in the camp that believed that the keyboard was always faster than mouse for complex workflows.
Then a couple of weeks ago I spent most of a day in a hospital emergency room with someone, and couldn't believe the way those E.R. nurses fly through the menus and options in Epic using just a mouse.
I'm now closer to believing that "muscle memory is muscle memory." But I suspect it only works if the windows appear in the exact same place all the time.
- https://github.com/moverest/wl-kbptr
- https://github.com/petoncle/mousemaster
- https://github.com/y3owk1n/neru
- https://github.com/mjrusso/scoot
- https://github.com/jbensmann/mouseless
- https://github.com/rvaiya/warpd (not really maintained anymore)
...which supports Vimium-style hints mode as well as the grid-based approach shown in this "Mouseless (app) explained in 80 seconds" video. It also has a very responsive maintainer.
Personally I like vimium's approach much better than the grid. Unfortunately not everything has a good accessibility tree (Zed sadly doesn't), but I just realized loading neru's page that I'm behind in versions. I haven't tried the "Native Vision OCR" addition to hints mode yet.
I also like having a trackpad right on the keyboard (using a SoflePLUS2 right now though I'm not totally sold on column stagger). Then I can use a real pointing device with only a slight movement of one hand. In the Mouseless video, the creator has tried to minimize the distance by putting the mouse between the halves of his keyboard, but I think he's both compromised the keyboard position to ease using the mouse (arms wide and parallel with wrists turned inward rather than arms converging toward a more splayed keyboard with somewhat closer halves, untented to minimize vertical separation compared to the mouse) and might have an uncomfortably small mousepad to avoid doing this even more. Not a compromise I'd want to make.
Free and open source is important and it's perfectly fine to be critical here.
It's like vimium but for your entire mac. It hooks into the macOS accessibility APIs.
I use the pointer stick exclusively so don't have to reposition my hands on the keyboard like with a track pad, but the pointer stick does keep my hardware choice limited, currently a X1 Yoga. If Mouseless would be faster, then I could get a Framework (no pointer stick available).
I'd gladly pay the $50 for lifetime.
I don't understand why they are not popular at all and only a few manufacturers build them.
It doesn't replace a mouse for me, but the track point is between the G H B keys and can be reached without moving the fingers away from the typing position. So it's great for some simple mouse commands.
Because they are ugly, just like ThinkPads that include them.
(not affiliated, just a happy user for years now)
Hell - after installing, it shows a slider to help adjust the label size of each element - but I can't slide it because (surprise) Homerow doesn't support horizontal slider elements like this.
I also can't highlight text on the screen etc.
Struggling to find a usecase for Homerow that isn't just navigating chrome or my filesystem.
There is an extensive list of window managers, like Sway or I3, file managers like Vifm and Ranger and browsers like Luakit.
I consider myself a "keyboard power user" if this is a thing anyway, and I really dig the home row thing (Vimmer for 20+ years now), but frankly having my hands on the keyboard ALL the time throughout the day is really tiring. So, I actually like my mouse for a change of posture, the cursor that I can follow with my eyes, etc.
P.S. I have to admit, though, that I love even more the interfaces that don't require a mouse in the first place. It's a shame we stopped adding well-thought tab stops in the UI and keyboards shortcuts are just a free-for-all in the apps.
Disclaimer: I'm one of the authors/maintainers.
I agree that I would never pay a subscription fee for any kind of system functionality, but there is a lifetime purchase option available, so there is no grounds to critique that here. Having extra payments models available in addition to a regular purchase model does not make a product worse.
Qutebrowser was my favorite browser for keyboard navigation but firefox, chrome, etc. have extensions for this as well.
I really feel like this used to be the default. That's how I always did it in macOS going back to the early 2000's.
Only in the last two versions or so did I notice it was no longer the default. I'm glad to see here that I can now re-enable it.
Edit: I see that I do have it enabled. But for some reason there are a lot of programs where it doesn't seem to work anymore, no matter what the settings. Off the top of my head: Half the Adobe programs I use for work.