Re: Setting default server
On 2018-03-20 08:43 +0000, David Griffith wrote:
> On Mon, 12 Mar 2018, Christoph Lohmann wrote:
>
> > Greetings,
> >
> > On Mon, 12 Mar 2018 18:38:50 +0100 David Griffith <dave@661.org> wrote:
> >> On Mon, 12 Mar 2018, Christoph Lohmann wrote:
> >>> I have added a workaround at /Software/Gopher to present the gopher+ re???
> >>> direct in geomyidae now too. You should be redirected to the root of go???
> >>> pherproject.org now. gopher(1) was sending no hint of expecting a go???
> >>> pher+ reply when requesting its default host. The default host is com???
> >>> piled into the kernel. If you recompile just use some alternative gopher
> >>> client.
> >>
> >> What is the workaround you added? Is there still a way to set the default
> >> page in $HOME/.gopherrc or /etc/gopherrc?
> >
> > I added the link mentioned in the thread below to have a redirect from
> > gopher+ to gopher at gopherproject.org. You can configure your local go???
> > pher(1) to your will in gopherrc.
> >
> > For setting it in the gopherrc the syntax seems to be specified via set???
> > ting »home:«. You can read the details of the following lines in the GS???
> > fromLink() function in GSgopherobj.c.
> >
> > As Kim said, gopher(1) is not backwards compatible to gopher+. Gopher+
> > is a really ugly and not really thought out protocol. Only people using
> > the original client will see the redirect until people have switched
> > over to saner clients like sacc(1).
>
> I still like the look and feel of the standard gopher(1) client. Is there
> some way to add gopher+ support to it?
I think the problem is the presence of gopher+ support (and the way in
which it is used), not its absence (Christoph, did you mean "backwards
compatible to gopher" instead of "... gopher+"?).
--
Nuno Silva
Reply to: