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] protocol handlers and outputting to buffer
Date: Sun, 11 Feb 2018 11:54:53 -0500	[thread overview]
Message-ID: <20180111115453.eklhad@comcast.net> (raw)
In-Reply-To: <20180211164142.x5wa46v7wuzz7dmp@toaster>

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

Thank you for raising this issue.
Edbrowse has native support for ftp, but ftp has no headers and no help, so edbrowse is a bit limited in its understanding, as is every other ftp client.
I know what you mean about a gopher menu, ftp presents each directory as a menu, showing subdirectories and files.
Clients understand this, as does edbrowse.
I turn a menu listing into html, with links, ftp links, that take you to subdirectories and/or files.
It works pretty well.
I imagine something like that could be done for gopher, and I'd say it has to be native, like ftp, I don't think this is a plugin situation.
I'll play around with the public gopher sites as time permits,
this is something edbrowse should do.

Karl Dahlke

  reply	other threads:[~2018-02-11 16:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26 18:01 Adam Thompson
2018-01-26 18:13 ` Karl Dahlke
2018-01-27  9:58   ` Adam Thompson
2018-01-27 14:40     ` Karl Dahlke
2018-02-01 19:58       ` Adam Thompson
2018-02-01 20:28         ` Karl Dahlke
2018-02-09 18:44           ` Adam Thompson
2018-02-09 20:10             ` Karl Dahlke
2018-02-11 16:41               ` Adam Thompson
2018-02-11 16:54                 ` Karl Dahlke [this message]
2018-02-11 17:14                   ` Adam Thompson
2018-02-11 17:40                     ` 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

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

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).