edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] gopher start
Date: Wed, 28 Feb 2018 11:04:33 -0500	[thread overview]
Message-ID: <20180128110433.eklhad@comcast.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 717 bytes --]

This is mostly for Adam but anyone else is welcome to chime in.
I did some foundational work for gopher, but don't know much about the protocol, and was too lazy to read the manual, just looked at the home page and figured a few things out.
So there is more work to do of course. Meantime...

edbrowse gopher://gopher.club

It's a properly formatted listing with hyperlinks, but,
click on the first link and it says
/hlogs/ does not exist, but I tried to access /phlogs/.
If you unbrowse and look, that's what the html says.
So why did the p get lost? And is that why the resource can't be found?
Perhaps my lack of gopher knowledge is showing here; but hey, we can bring up the home page.

Karl Dahlke

             reply	other threads:[~2018-02-28 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 16:04 Karl Dahlke [this message]
2018-03-03  2:33 ` Kevin Carhart
2018-03-09 20:44   ` Adam Thompson
2018-03-09 20:50     ` Karl Dahlke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180128110433.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).