Re: gopher2html, a possible way to browse the gopherspace via w3m
On 1/23/18, Leonardo Taccari <iamleot@gmail.com> wrote:
> Hello to the entire Gopher community!
> As an exercise in reading RFC 1436 I have written a simple AWK
> script that I use to browse the gopherspace via w3m.
>
> Under the hood it uses siteconf (~/.w3m/siteconf by default) and
> local CGI scripts support in w3m (if you would like to learn more
> about them please give a look to README.siteconf and the w3m manual
> provided by w3m).
>
> siteconf permits to rewrite URLs so all gopher:// URLs are
> passed to the gopher2html.cgi local CGI script invoked by w3m.
> gopher2html.cgi just uses curl and then pipe the response to
> gopher2html that renders it in HTML.
>
nice! if you want to take it to the next level you could try patching
w3m to support gopher by default, and trying to get it accepted
upstream. this is would solve the problem for everyone without adding
additional software to install/keep track of. plus it wouldn't have
to rely on HTML - not depending on HTML is one of the great things
about gopher.
best,
caleb
Reply to: