gopher "go to parent" renders parent as raw text - no links | bug | nightly build | osx

[lefou23]

Loading a gopher link, then navigating to its parent results in text, with the first character often a '0' or 'I', presumably gopher identifiers for links on that line.

Example steps:

• navigate to gopher://sdf.org:70/1/users/rbigelo/

  

• click one of the links, Gopher, for example

• go to parent

the resulting document is now text only

not sure if this is Mac OSX issue only or all gopher

used the Mac OS nightly build from 2023-10-01 macOS (dmg, x86_64, unsigned)

Mac OS:

Sorry, don't know how to add labels, like bug, gopher, osx

[ikskuh]

Looks like Go to parent should be disabled on Gopher as the URL encodes the file type, and we cannot know the parent file type. It most likely will be a directory/list, but we cannot be safe about that

[lefou23]

I think Gopher was intended to be very simple - Servers return either directory lists or "documents". My attempt at being logical: A parent to a document would always be a text menu (directory list), unless the client is already at the "top" level of a server path.

Presumably the "connection closed" or timeout error is the old school way to know if there was anything at that address or not. I will do more research on the protocol if that would be helpful.

I hope you'll reconsider disabling the "go to parent", unless disabling is a temporary solution, or the problem space is bigger than I understand. If you choose to disable it, perhaps convert this issue to a feature request?

I really like Kristall for its capabilities to handle gemini, gopher, and http(s). Haven't experimented with finger, but I like what I see very much in these other protocols. Thank you for all your work so far, and making it freely available.