Live data from Hacker News

A mouseless tale: trying for a keyboard-driven desktop

lwn.net

81–90 of 111 posts

Re: A mouseless tale: trying for a keyboard-driven desktop

#81

I recently rediscovered Ratpoison WM and the origin of its name (tl;dr it is meant to prevent the need for using a mouse). I think the main issue for me really is that navigating the web is sometimes faster with a pointer. I already use vim and the shell for everything else, but navigating Google Maps or Wikipedia or Stack Overflow is just easier when you can point and scroll.

Have you tried Vimium or something similar?

Re: A mouseless tale: trying for a keyboard-driven desktop

#82
post #45
post #9

Earlier quoted context omitted.

You may be thinking of [Homerow]( https://www.homerow.app/ ) for Macos. Its okay for popups that I used to need a mouse for. There's another app that does similar "Vimium for Desktop" but it wasn't as responsive and sometimes focus would get stuck, but I forgot that software's name.

Oh nice, thanks for sharing this. I don't think it was homerow (or it has evolved a lot). I'll give this one a go to see if this helps me touch less my mouse

You might be thinking of Shortcat. I've been using it for a while and it mostly works but doesn't seem as polished as Homerow. Going to give that one a try now.

https://shortcat.app

Re: A mouseless tale: trying for a keyboard-driven desktop

#83
If you're keen on the ideas of PaperWM, but don't want to lug GNOME around for the ride, niri is great: https://github.com/YaLTeR/niri

(Though I personally drive niri with a lot of touchpad gestures. Three-finger swipes up/down/left/right etc are great.)

Re: A mouseless tale: trying for a keyboard-driven desktop

#84
post #38
post #25

This is one of the things that pisses me off about MacOS. Every other majot OS out there at least offers a good failsafe keyboard navigation built in to each UI component. In a pinch, the keyboard is your friend, at least until your pointing device is back up. MacOS: lol, sorry, bluetooth settings require a pointing device to add a new one. Keyboard navigation? Sure. It worked up until this part, but we didn't bother…

Did you enable this setting? If yes, can you tell me more what's missing? https://support.apple.com/en-us/guide/mac-help/mchlc06d1059/...

What's missing is discoverability -- something Apple used to claim to care about.

Re: A mouseless tale: trying for a keyboard-driven desktop

#85
post #25

This is one of the things that pisses me off about MacOS. Every other majot OS out there at least offers a good failsafe keyboard navigation built in to each UI component. In a pinch, the keyboard is your friend, at least until your pointing device is back up. MacOS: lol, sorry, bluetooth settings require a pointing device to add a new one. Keyboard navigation? Sure. It worked up until this part, but we didn't bother…

Had to use a Mac at a job last year. It wasn't used much so the mouse wasn't charged. Why oh why is the mouse unusable when it's charging!?

Supposedly it's by design. The justification being something along the lines of "you're doing it wrong" if you have to drag the cable around while mousing.

Re: A mouseless tale: trying for a keyboard-driven desktop

#86
I've been forced by some shoulder issues to reevaluate how I use the computer. My issues seem to mostly be from external rotation of the arm (i.e go from keyboard to mouse movement), though I've had some wrist issues before as well. That's gotten better, but it's still not great.

Not sure what I'll try. Split ergo keyboard maybe, and try to get my development workflow to work as mouselessly as possible. I only wish nvim worked better with Java. It's still a bit too flakey. Painfully almost works. Maybe there are some Idea plugins or somethng.

Re: A mouseless tale: trying for a keyboard-driven desktop

#87
post #25

This is one of the things that pisses me off about MacOS. Every other majot OS out there at least offers a good failsafe keyboard navigation built in to each UI component. In a pinch, the keyboard is your friend, at least until your pointing device is back up. MacOS: lol, sorry, bluetooth settings require a pointing device to add a new one. Keyboard navigation? Sure. It worked up until this part, but we didn't bother…

It's not ALL bad, when I recently replaced my 2012 MacBook Pro with a 2024 Air M3, I was pleased to see that Apple FINALLY allows tabbing in system pop menus for things like Save, Delete, Close and selecting those options with the Space bar. Not sure when that was added as default behaviour, but I always found this frustrating coming from Windows. The interesting thing is that precisely one app I used on the 2012 MBP - Ableton Live Digital Audio Workstation - always allowed keying through popups flawlessly - so the underlying capability was there.

Re: A mouseless tale: trying for a keyboard-driven desktop

#88
It speaks a lot about tiling. One thing I hate about the current "tiling" options in mainstream desktops, like windows, Mac and even KDE, is that they're so half baked. You can tile windows side by side but then if I make one window a bit narrower to make an uneven split, I still have to manually resize the other one :( That's not tiling.

Re: A mouseless tale: trying for a keyboard-driven desktop

#89
post #25

This is one of the things that pisses me off about MacOS. Every other majot OS out there at least offers a good failsafe keyboard navigation built in to each UI component. In a pinch, the keyboard is your friend, at least until your pointing device is back up. MacOS: lol, sorry, bluetooth settings require a pointing device to add a new one. Keyboard navigation? Sure. It worked up until this part, but we didn't bother…

macOS also really had great keyboards shortcuts. Maybe even more than Windows. But Apple also plastered them over :(

Re: A mouseless tale: trying for a keyboard-driven desktop

#90
post #63

Earlier quoted context omitted.

The worst for me is being able to select the non-default option in an alert window. Sometimes CMD + 'the first letter of the word in the button' works, but that's like a 30% chance. How is there not a standard for that? I'd even accept the arrow keys + Enter at this point.

> How is there not a standard for that? There was, long ago, in the Macintosh Human Interface Guidelines.

Which apple always sets an example for by not following.
Post reply on HN