The second part of the quick tour starts with a fresh gc session by contacting a Gopher+ server:
./gc -e al:0 'gopher://localhost:2070/1/client%09%09$'
This time the URL on the command line uses gopher:// scheme, therefore
1is the Gopher item's type indicator and required to tell gc that it is going to load a directory,
%09are replaced with <tab> characters, and
$makes gc request a Gopher with all Gopher+ attributes (or unprecisely but short: a Gopher+ directory) from the server. Two <tabs> are the correct of doing that way, even if the selector has only one.
The type indicator is only required if a particular item from the
server is retrieved. If the server's root (the server's "home page")
gopher://localhost:2070/%09%09$ would be sufficient.
Now what is the result with the request from above?
The directory looks similar to the one from part 1 and the only difference is that this one has some more entries. The screenshots are not labelled as images (this goes right now to my todo list) but the rest looks like it should.
Display the Gopher+ information from item 7:
= is an alias for the
plus command and can be combined with a
directory item. The server's Gopher+ information is pretty standard:
the +INFO: and +ADMIN: block, alternative views. They are Gopher+
standard and there's no -VIEWS: because we are talking to a real
Gopher server instead of fetching things from an HTTP-server. Then
there are related items. We met them already in the previous part.
However, this is the prev/next information (pnx) from the server.
gc is computing its own which might differ (and right now the server
is doing it wrong). This make an important difference when the
directory of the result of a search. gc will the order the items
as they are listed while the Gopher+ information shows links in the
context of their location on the server.
I mentioned that I find that directories are important and that's also
reflected in gc. Directories are the navigation anchor and in
addition to the current document gc holds also the last Gopher
directory in its memory. That means for instance, if you remember an
item's number in the directory you can open that by entering
would open gc's main page.
Now let's open the Gopher RFC on the Internet.
You could easily start to move around following any of the hyperlinks in the document. (There are no really interesting links but the RFC is just an example.) A place where you can easily get lost is Gemini space.
You can visit as much web pages as you like and gc holds still the
last directory, which you can list with
ls. This brings you back to
the place where you left the Gopherspace and should be very handy when
you have done a search before.