I'm making a concerted effort to use Qutebrowser again. I genuinely like this browser and any quirks I come across I am ironing out as they pop up their head.
I'm making a concerted effort to use Qutebrowser again. I genuinely like this browser and any quirks I come across I am ironing out as they pop up their head.
I want to use keyboard driven website quite a while, So far i tried #qutebrowser
#nyxt but i couldn't use it after a while so i stayed in #librewolf for a long time. until i stumble across #glidebrowser in @idlip blog on EWM. Immediately switched to it.
Reason:
- Firefox fork
- Customizable through typescript
- Support Emacs key binding (taken the code from Github discussion).
Have some issues here and there but it's awesome.
Upgraded another machine to @fedora 44. Upgrade went well, no issues. #Qutebrowser on this machine wouldn't launch. Looks like an issue #QT and GPUs, since this one has an #Nvidia GPU. Workaround seems to be to play with an environment variable. This worked for me: `QTWEBENGINE_FORCE_USE_GBM=1 qutebrowser`
References:
gw pengen pakai #qutebrowser untuk browsing tipis - tipis dibandingkan harus pakai chrome atau firefox. Ternyata ukuran installer untuk mac silicon sekarang lebih dari 170Mb. Kalo diurai bisa jadi malah bengkak ke 300Mb.
Sudah ga bisa disebut tipis lagi ha ha ha
Having a wonderful start with #qutebrowser 
I use the #Dvorak keyboard layout, so using H, J, K & L for navigation makes little sense compared to D, H, T & N!
Thanks to qutebrowser's powerful configuration system, I've been able to move all the default keys to Dvorak-friendly alternatives.
Bravo @the_compiler, and thank you so much for a wonderful project!