1. Forum
  2. USENET
  3. comp.infosystems.gopher

  • text does not scroll in original gopher, but in lynx

    From Marco Moock@mo01@posteo.de to comp.infosystems.gopher on Thu Oct 27 14:41:20 2022
    From Newsgroup: comp.infosystems.gopher

    Hello,

    when I go to gopher://gopher.black --> Phlog --> 2022-06-26 - Abortion
    I can scroll the text in lynx, but not in the application "gopher" on
    Ubuntu. In can scroll other text in gopher holes with "gopher".

    Do other people also experience that?
    --
    kind regards
    Marco

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Mateusz Viste@mateusz@xyz.invalid to comp.infosystems.gopher on Thu Oct 27 15:18:11 2022
    From Newsgroup: comp.infosystems.gopher

    2022-10-27 at 14:41 +0200, Marco Moock wrote:
    when I go to gopher://gopher.black --> Phlog --> 2022-06-26 - Abortion
    I can scroll the text in lynx, but not in the application "gopher" on
    Ubuntu. In can scroll other text in gopher holes with "gopher".

    Do other people also experience that?

    Works fine for me using the Linux gopherus client https://gopherus.sourceforge.net

    I looked at the mentioned article with telnet and it looks like a
    perfectly good Gopher menu to me. You might want to report the issue to
    the author of this client you use.


    Mateusz

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From not@not@telling.you.invalid (Computer Nerd Kev) to comp.infosystems.gopher on Fri Oct 28 07:22:31 2022
    From Newsgroup: comp.infosystems.gopher

    Marco Moock <mo01@posteo.de> wrote:

    when I go to gopher://gopher.black --> Phlog --> 2022-06-26 - Abortion
    I can scroll the text in lynx, but not in the application "gopher" on
    Ubuntu. In can scroll other text in gopher holes with "gopher".

    Do other people also experience that?

    Yes that's a known bug in the UMN Gopher client. Alternatively as
    that client is somewhat official because it was written by the
    creators of the protocol, one might argue that it's really that
    gophermap which is buggy. But it's a common problem.

    The issue is that gophermaps weren't intended to contain long text
    content - it was always supposed to be in a plain text (item type
    0) file. So, presumably becuase there weren't any gophermaps like
    that around back in the day, the navigation system was never
    designed to handle them. This affects both gophermaps with no
    links, like that one, and those with more than one page-length of
    text between links, because the only way to navigate is to move
    between links.

    One clunky solution is to press "shift-S", which allows saving the
    current gophermap to file, whereafter you can view it with Less.

    There was a patched version _somewhere_, but either the author
    removed it or I forgot who they were (probably the latter).
    --
    __ __
    #_ < |\| |< _#
    --- Synchronet 3.21d-Linux NewsLink 1.2