On Fri, Feb 09, 2018 at 03:10:24PM -0500, Karl Dahlke wrote: > curl has gopher support. > Tell edbrowse to use curl to download anything gopher, just as it downloads > http or https. > Look at http.c line 937, perhaps we can just add gopher to the disjunction. > Perhaps headers will come across, like http headers, with content type, and > of course the file could have suffixes. > I'd play around with it but don't have a gopher server with various files to > test. > Unless there is a public one. > Just change that one line and run with db4 and see what kind of headers come > across.
Yeah I know, I was contemplating patching the support directly into edbrowse but wasn't sure which would be easier plus it'd be good if plugins could more closely integrate with the rest of edbrowse in any case. On the subject of gopher specifically it has no headers, the content type is done in the selector. It also has a menu which needs to be parsed (basically a list of selectors and text). Quite simple but would need the rendering code to be aware of it somehow. I'm not sure if I could do something like the ftp code? Anyway, sdf.org (and sdf-eu.org) run a gopher server, and there're a bunch more (including a project gutenberg one but I'm not sure how standard that one is). Cheers, Adam. _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
