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.
A mouseless tale: trying for a keyboard-driven desktop
81–90 of 111 posts
Re: A mouseless tale: trying for a keyboard-driven desktop
#82Earlier 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
Re: A mouseless tale: trying for a keyboard-driven desktop
#83(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
#84This 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/...
Re: A mouseless tale: trying for a keyboard-driven desktop
#85This 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!?
Re: A mouseless tale: trying for a keyboard-driven desktop
#86Not 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
#87This 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…
Re: A mouseless tale: trying for a keyboard-driven desktop
#88Re: A mouseless tale: trying for a keyboard-driven desktop
#89This 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…
Re: A mouseless tale: trying for a keyboard-driven desktop
#90Earlier 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.