Command line gopher client. High speed, low drag.
Ideally, you would install VF-1 as follows:
pip3 install VF-1
This should install the command
vf1 in either
Alternatively, check out the source code and install it as follows:
pip3 install .
If you're a developer, you probably want an "editable" installation:
pip3 install --editable .
If you're a developer on a Windows machine and your pip is broken, you can also install as follows:
python3 setup.py install
And finally, if you just can't install it, just run the
Start VF-1 with your bookmarks:
Start VF-1 with your favourite site:
Quick, informal tutorial-style introduction
VF-1 is built around an interactive command prompt, and has a very "REPL" feeling. You only need a small number of commands to get around, and most of them can be abbreviated to one or two chars, so with practice you can get around very quickly. You can safely unplug your mouse the entire time you are using VF-1. :)
Well, let's start off by heading to SDF to check out some nice phlogs! Use the "go" command:
VF-1> go sdf.org/
(don't leave off the trailing slash - this won't be necessary in future releases, but right now it is required for technical reasons I won't get into)
(if you are very lazy, you can type "g sdf.org/" instead, i.e. you can abbreviate "go" to "g")
You should see a listing of the SDF Gopherspace. The different menu items are indicated by numbers in square brackets, and the SDF Member PHLOGOSPHERE is option , so go ahead and type "1" and then enter:
You should see all the phlogs fly by, and unless you have a very large monitor some have probably run off the top of the screen. This will not be an uncommon problem, and there are various ways to deal with it. Obviously, you can scroll up in your terminal like always, but VF-1 gives you other ways to deal with this. After you have visited a gopher menu (as opposed to a document), if you just press Enter (i.e. execute an empty line), VF-1 will print the first 10 items in the menu by themselves (any ASCII art etc. in the original listing is removed in this mode). Each time you press enter you will see the next ten items in the listing. Page through a few times to get a feel for it.
If you just want to see which phlogs have been updated lately, that's probably enough for you. But suppose you are really curious about one phlog in particular. Say you want to know what Tomasino has been up to. You could search for his phlog specifically:
VF-1> search tom
(if you are very lazy, you can use "/" instead of "search", i.e. "/ tom")
This will show you the phlogs with "tom" in them (it's a simple case-insensitive search). Tomasino will probably be  or  (depends whether tomatobodhi has updated more recently :). So go ahead and type "1" and hit enter again to enter Tomasino's gopherhole. Then you can type "2" and enter to go to his phlog, and then "1" and enter to read his most recent entry about Kindles.
Suppose now you want to go back to the main SDF phlog listing. Let's check out your history:
(if you are very lazy, you can abbreviate "history" to "hist", and in fact if you are fiendishly lazy you can just use "h")
You should this time see a menu of the few places you've been so far. The phlogosphere list will probably be , so type "2" and enter to go back there. By now you are probably getting the hang of using numbers to get around.
For this next bit, let's focus on gunnarfrost's phlog, because he writes very nice short entries which work well for this. Once you're at the main phlog listing, do a:
VF-1> search frost
To easily find gunnarfrost's phlog and then press  to type the first entry.
Short and sweet! Now, suppose you want to read his next post. You could use the "back" command to go back to the menu listing and then press "2", and then do "back" and "3", "back" and "4", etc. But it's much easier to just type:
(or, if you are lazy, just "n")
This will automatically take you to the next item in the most recently seen gopher menu after the one you just viewed. So you can just hit "n" and enter again and again to flip through the pages of gunnar's phlog. Each one is much shorter than a full screen, so this works very nicely.
Lately gunnarfrost is a good phlogger and wraps his entries at 70 or 80 chars or thereabouts. But if you keep hitting "n" you'll get to early entries where the lines just keep going until your terminal wraps them (sorry, gunnarfrost, I don't mean to single you out here, plenty of other folk do this too!). Once you've found one of these, try running:
And VF-1 will wrap the lines at 80 chars for you (assuming you have the "fold" command installed on whatever system you are using). This isn't the only helper command of this kind available. Get back to the main SDF phlog listing (either by running "back" a few times or using "hist" and a number to jump straight to it) and go to my phlog. Unlike gunnarfrost, I appear to be physiologically incapable of writing phlog posts which are less than a few whole screens long. Go to one of these posts (say my most recent "assorted replies and acknowledgements"), and watch the lines fly by. Now try:
This will pipe my giant entry through "less", so you can move back and forth and read it. Just press "q" when you're done like usual to get your VF-1 prompt back.
I have quite a few references at the end of that entry. You might be tempted to pick up your mouse, highlight those URLs, and use the "go" command to visit them. Put that rodent down! The mouse, that is, not the gopher. Instead, try this command:
VF-1 will then scan the most recently viewed post for URLs. Well, actually, it scans for words (i.e. things separated by spaces) which contain "://" and at least one ".". This might not catch all URLs and it might sometimes catch things which are not URLs, but it works well enough for now. You will see a menu and now you can use numbers to follow any of those links without your mouse!
If you want to know the URL of a document you are at so that you can refer to it, just do:
If you want to save the document, just do:
VF-1> save ~/some/random/path/somefilename.txt
Everything so far has been text-based. Gopher items with itemtype 0 (text) are fed to the "cat" command by default, or to "less" or "fold" if you request it. But VF-1 can handle other itemtypes too. Image files with an item type of "g" or "I" will be opened using the "feh" image viewer (if installed). HTML content with an item type of "h" will be fed to "lynx --dump", and audio files with an item type of "a" will be fed to "mpg123" (e.g. you can listen to jynx's doom metal songs in this way). Obviously if you do not have one of these programs installed, it will not work. In future I may provide some nice way to customise which 3rd party programs are used for different item types. For now, if you want to use different programs, you will have to edit the code. It's not hard, just look for the _HANDLERS dictionary near the top of vf1.py and change accordingly.
You probably need some bookmarks, right? Here's how to add the current URL to your bookmarks. You can provide your own name, if you want.
(or, if you are as lazy as usual, just "a")
If you want to reorganize your bookmarks, just open
~/.vf1-bookmarks.txt using a text editor and do it.
If you want to look at your bookmarks:
(or, if you feel comfortably lazy, just "bm")
Sometimes you're looking at a menu and it's very long but you know you
want to look at few items, one after another. Assume you're looking at
phlogosphere.org, for example. How about adding the first four items
to a tour and then going on that tour?
VF-1> tour 1 2 3 4 VF-1> tour
Use the tour command without any arguments to go to the next stop. This is basically your stack of items to go to. (And yes, you guessed it. Use "t" if you're feeling lazy.)
Actually, if you're really lazy, you can use ranges, too:
VF-1> tour 1-4 VF-1> tour
But there's more. Let's say you're looking at something pretty
interesting, like the list of all the phlogs on
How about marking this place with a letter, following some links, and
then returning to this location not using a bunch of "back" and "up"
commands but just that one letter?
VF-1> mark x VF-1> ... do some stuff ... VF-1> go x
(And yes, "m" for the lazy.)
To make a few implicit concepts explicit:
- VF-1 always has in it's mind exactly one "index", i.e. a list of places in Gopherspace with numbers attached to them. By typing "1" and enter, "2" and enter, etc. you jump to that location in the active index.
- Whenever you visit a gopher menu, the contents of that menu become the active index, replacing whatever it used to be.
- When you do "search" or "history" or "links", the results of these commands overwrite your current index. If you want to get your index back to being the most recently visited gopher menu, you can use the "ls" command. Doing this means you lose your search results (your history doesn't go away, though).
- The "search" command runs on whatever the current index is. This might not be the contents of a gopher menu. You can search your history, and in fact you can even search the results of an earlier search to narrow things down!
- In general, VF-1 does not remember much. It always has some idea of the most recently visited gopher menu (i.e. itemtype 1) and the most recently visited gopher document (i.e. any other itemtype). "ls" always operates on the most recently visited gopher menu, even if you have visited some documents since then. Commands like "fold", "less" and "save" operate on the most recently visited document, even if you have visited some menus since then. Basically everything operates one the most recently seen thing of the appropriate type.
VF-1 uses external programs as "handlers" to present gopherspace content to you.
Even when you visit a plain text file with item type 0, VF-1 spawns (by default)
the unix command
cat to display that file on your screen, rather than using a
Handlers are assigned on the basis of MIME types. The gopher protocol has no concept of MIME, so VF-1 assigns each item a MIME type as follows:
- Item types 0 and 1 are assigned MIME type
- Item type h is assigned MIME type
- Item type g is assigned MIME type
For all other item types, VF-1 attempts to guess a MIME type from the file extension of the last component of the selector, using the mimetypes module from the Python standard library. This usually results in a reliable identification assuming the file has an extension and the author of the gopehr content is not actively trying to deceive you.
If the selector has no file extension, or the extension is not recognised by the
itemtypes module, VF-1 will use the unix program
file to attempt to guess a
MIME type by actually inspecting the content of the file.
In accordance with the idea that gopher item types, which are a standard part of the protocol, should take precedence over any other attempt at inferring MIME type, which is not a standard part of the protocol, if an item in gopherspace is listed with itemtype "I" or "s" and one of the above methods returns a MIME type which does not begin with "image/" or "sound/" respectively, VF-1 will default to "image/jpeg" or "audio/mpeg" respectively. This should only happen in highly unusual circumstances and suggests a poorly or maliciously configured gopher server.
Once a MIME type has been identified for an item, an appropriate handler program
will be used to handle the content. You can view a list of the current handler
assignments at any time by running the
handler command. The default handlers
that ship with VF-1 are:
lynx -dump -force_html %s"
You can also use the
handler command to change these handlers, or set handlers
for new MIME types For example, if you prefer using
handling HTML content, you could run:
VF-1> handler text/html w3m -dump %s
You can use the
* wildcard when specifying handler MIME types, such as
image/* to use a single program to handle any kind of image. Handlers
without wildcards take precedence over handlers with wildcards. In other
words, if you specify, e.g. one handler for
image/jpeg and a different handler
image/jpeg handler will be used for JPEGs and the
image/* handler will be used for all other
VF-1 attempts to decode the content received for any text-based item types (e.g. 0, 1, 7, h) as UTF-8. Most content in gopherspace is ASCII-encoded, and since UTF-8 is backward compatible with ASCII, this will generally "just work". If the received content cannot be decoded as UTF-8, one of two possible things will happen.
If the chardet Python module is installed on your system, VF-1 will use it to attempt to automatically detect the encoding used and decode the text appropriately. Note that pip etc. will not install chardet for you when you install VF-1, as VF-1 does not formally depend on chardet. It uses it opportunistically, so that it can still be easily installed and used on systems where chardet is not / cannot be installed.
If chardet is not installed, or if chardet cannot identify an encoding with confidence exceeding 0.5, VF-1 will attempt to fall back to a single, user-specified alternative encoding. This encoding can be set with, e.g.:
VF-1> set encoding koi8-r
The default fall back encoding is iso-8559-1, which is used by the popular gopher site floodgap.com. If you routinely visit gopher sites encoded with some other encoding, consider using an RC file (see below) to automatically set your alternative encoding at start up.
Upon startup, VF-1 will search for a file with one of the following names:
The names are listed above in order of preference and VF-1 will stop after the
first one it finds, e.g. if you have both a
~/.config/vf1/vf1rc and a
~/.vf1rc will be ignored.
If such a file is found, each line of the file will be executed as a VF-1 command before the prompt is displayed. This allows you to script certain commands that you want to be run every time you start VF-1. This lets you:
- Permanently configure item type handlers by putting
handlercommands in the RC file.
- Permanently configure any options, such as whether or not to use coloured
output or your preferred non-UTF-8 encoding, by putting
setcommands in the RC file.
- Set a "home page" by putting a
gocommand in the RC file.
- Start a tour through your favourite sites by putting
tourcommands in the RC file.