3 ms·
I really like the idea of Nyxt, but I had trouble using/scripting it in practice last time I tried (back in June). IIRC, my issues were: 1) Vim keybindings be
by senkora 3y ago
I really like the idea of Nyxt, but I had trouble using/scripting it in practice last time I tried (back in June).
IIRC, my issues were:
1) Vim keybindings being somewhat clumsier than using Vimium on Chrome
2) Flatpak being tricky to use (I think this was just my own unfamiliarity)
3) I never figured out if it had emacs-style introspective documentation (e.g. describe-key, describe-function)
4) I couldn't get restore-history-by-name to work (save-history-by-name did work).
My plan was to script Nyxt in order to write my own session manager, by saving/restoring named histories. Then, I could associate them with emacs desktop sessions and JIRA tasks to improve my ability to stop/resume/look back at tasks.
Ultimately, I found that the Session Buddy extension for Chrome was a better fit for my use case (and it stores its session in a sqlite database that was easy to query programmatically).
The other thing that I tried was directly querying Chrome's session files for a list of tabs, but this was unreliable (the file was often out of date and didn't include suspended tabs). Supposedly it's possible to get a correct tab list on MacOS via Applescript.
All of which is to say, Nyxt looks great and I hope it keeps getting better and I encourage others to try it, but the last time that I personally tried it I ended up concluding that Chrome+Vimium+SessionBuddy was a better fit for what I wanted out of my browser.