edbrowse is awesome. I fear that most people, like OP in this case, don’t really understand the difference between "TUI" (where a terminal is used to display a GUI) and "CLI", where every interaction is a written command resulting in a output.
I’ve a perfect sight myself but I really like the comfort of linearity with CLI: I ask my computer something, I receive an answer.
(that’s probably why I’m developping my own CLI browser but is more graphical and less advanced than edbrowse)
> I fear that most people, like OP in this case, don’t really understand the difference between "TUI" (where a terminal is used to display a GUI) and "CLI", where every interaction is a written command resulting in a output.
I'm not sure how you could infer that, since OP didn't mention "TUI" or "GUI" or "CLI" anywhere in this post, and a text-based browser UI could come in either form.
So based on the first paragraph, I would’ve assumed “CLI” and “graphical” were mutually exclusive? Did you in fact mean to type “TUI” here? Or is your program something like a hybrid between command-based input and graphical output?
No, Offpunk it's command line driven, it just happens it can output images due to sixel support (and maybe in a near future with the w3m's image displaying tool).
I’ve a perfect sight myself but I really like the comfort of linearity with CLI: I ask my computer something, I receive an answer.
(that’s probably why I’m developping my own CLI browser but is more graphical and less advanced than edbrowse)