Nyxt Browser
11–20 of 134 posts
Re: Nyxt Browser
#12Every web browser should have a tree based history by this point. This part is cool: > Nyxt is web engine agnostic. We utilize a minimal API to interface to any web engine. This makes us flexible and resilient to changes in the web landscape. Currently, we support WebKit and WebEngine (Blink). Does this browser have anything do to with Next? The logo seems similar.
1. It just has bad KHTML forks for the engine. What about Gecko and Presto and Trident all the other fine renderers?
2. I don't know what kind of lisp they're using (probably Common Lisp), anyway it's not my favourite kind.
Re: Nyxt Browser
#13It even uses the same terminology with words like “buffers” instead of tabs.
Is this actually an Emacs-based browser being shipped to the masses?
Re: Nyxt Browser
#14I'll look at this again when they support gecko
Re: Nyxt Browser
#15That looks like someone bundled a prepacked browser-like starter-package using Emacs compiled with GTK-widgets (WebView) with Helm and some other niceties like the status-bar. It even uses the same terminology with words like “buffers” instead of tabs. Is this actually an Emacs-based browser being shipped to the masses?
Re: Nyxt Browser
#16Re: Nyxt Browser
#17I'll look at this again when they support gecko
Re: Nyxt Browser
#18I didn’t expect too many clever features but the special link hot keys and tree based history is something I didn’t know I wanted but now I do
Re: Nyxt Browser
#19I seem to recall that web pages were steadily making it harder for it to work. E.g no "a href" or "link rel"s.
Here's hoping that Nyxt will have success in bringing this era back!
Re: Nyxt Browser
#20Very excited at the idea of having fast fuzzy switching of tabs. I wish more things operated like that.