Setting default server

[David Griffith]

In the standard gopher client's manpage is this:

The [hostname] of a gopher server may be specified at startup; if
omitted, the default server for your site is used. You may also
specify a URL (Uniform Resource Locator) for this argument.

However, I find no description of how to set the default server in
anywhere in the manpages or source code to the gopher client.

Also, going through the source code, it looks like if I start the client
with no parameters, I should see gopherproject.org/Software/Gopher, but
instead I get "Nothing available" and then "gopher: Nothing received for
main menu, can't continue".

What am I missing?

[Christoph Lohmann]

Greetings.

Post by David Griffith
The [hostname] of a gopher server may be specified at startup; if
omitted, the default server for your site is used. You may also
specify a URL (Uniform Resource Locator) for this argument.
However, I find no description of how to set the default server in
anywhere in the manpages or source code to the gopher client.
Also, going through the source code, it looks like if I start the client
with no parameters, I should see gopherproject.org/Software/Gopher, but
instead I get "Nothing available" and then "gopher: Nothing received for
main menu, can't continue".
What am I missing?

Use sacc(1) instead, which gives you freedom.

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.


Sincerely,

Christoph Lohmann

[David Griffith]

Post by Christoph Lohmann
Greetings.

Post by David Griffith
The [hostname] of a gopher server may be specified at startup; if
omitted, the default server for your site is used. You may also
specify a URL (Uniform Resource Locator) for this argument.
However, I find no description of how to set the default server in
anywhere in the manpages or source code to the gopher client.
Also, going through the source code, it looks like if I start the client
with no parameters, I should see gopherproject.org/Software/Gopher, but
instead I get "Nothing available" and then "gopher: Nothing received for
main menu, can't continue".
What am I missing?

Use sacc(1) instead, which gives you freedom.
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?

[Christoph Lohmann]

Greetings,

Post by David Griffith

Post by Christoph Lohmann
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).


Sincerely,

Christoph Lohmann

[David Griffith]

Post by Christoph Lohmann
Greetings,

Post by David Griffith

Post by Christoph Lohmann
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?

[Nuno Silva]

Post by David Griffith

Post by Christoph Lohmann
Greetings,

Post by David Griffith

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+"?).

[Christoph Lohmann]

Greetings,

sorry for first sending off list.

Post by Nuno Silva

Post by David Griffith
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+"?).

For me gopher+ is the past so gopher(1) is still backwards compatible to
this old protocol which is not really thought out and represents the
reason why the web failed and gopher would fail too, if gopher+ is kept.

For David: My intention is to not support gopher+ since as said, it is
not well thought out and does not add any real value. The value of go???
pher nowadays is its simplicity. The real solution would be to take over
the maintainership of gopher(1) and remove the way it tries to use go???
pher+ first. The gopher+ support in gopher(1) is not thought out too. If
you use some URI gopher is used, if you only specify some host, gopher+
is used. If you specify everything with parameters gopher is used. Go???
pher+ has to die and gopher(1) is the last remaining bug. The redirect
in geomyidae is already a big hack to support this unclean gopher+ pro???
tocol.

Who is the maintainer of gopher(1)? I could provide a patch to remove
this annoying behaviour.


Sincerely,

Christoph Lohmann

[Nuno Silva]

Post by Christoph Lohmann

Post by Nuno Silva

Post by David Griffith
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+"?).

For me gopher+ is the past so gopher(1) is still backwards compatible to
this old protocol which is not really thought out and represents the
reason why the web failed and gopher would fail too, if gopher+ is kept.
For David: My intention is to not support gopher+ since as said, it is
not well thought out and does not add any real value. The value of go???
pher nowadays is its simplicity. The real solution would be to take over
the maintainership of gopher(1) and remove the way it tries to use go???
pher+ first. The gopher+ support in gopher(1) is not thought out too. If
you use some URI gopher is used, if you only specify some host, gopher+
is used. If you specify everything with parameters gopher is used. Go???
pher+ has to die and gopher(1) is the last remaining bug. The redirect
in geomyidae is already a big hack to support this unclean gopher+ pro???
tocol.
Who is the maintainer of gopher(1)? I could provide a patch to remove
this annoying behaviour.

jgoerzen (possibly the same John Goerzen from this list?) has the source
code for gopher(1) in github:

http://github.com/jgoerzen/gopher.git

The code appears to be GPL >=2.

[Bradley D. Thornton]

Post by David Griffith
David Griffith
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

I can't begin to express how vehemently this expresses  my sentiments.
--
Bradley D. Thornton
Manager Network Services
http://NorthTech.US
TEL: [phone]


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus