From a5157d1a3dc578819b9ee973f4755a8129e08284 Mon Sep 17 00:00:00 2001 From: Thomas Jensen Date: Thu, 29 Jan 2015 23:50:11 +0100 Subject: [PATCH] Update URLs --- FAQ.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/FAQ.md b/FAQ.md index 96d1382..7cc4adc 100644 --- a/FAQ.md +++ b/FAQ.md @@ -1,10 +1,10 @@ These are the frequently asked questions about the *boxes* program and their answers. -This document will only answer questions which are *really* "frequently asked". For general information on the *boxes* program, installation instructions, and information on box design creation please refer to the [documentation on the website](http://boxes.thomasjensen.com/docs/index.shtml). +This document will only answer questions which are *really* "frequently asked". For general information on the *boxes* program, installation instructions, and information on box design creation please refer to the [documentation on the website](http://boxes.thomasjensen.com/docs/). ###Q. 1. What is a text filter program? -**Answer:** There is a [separate page](http://boxes.thomasjensen.com/docs/filters.shtml) explaining this. *Boxes* is mostly used as a filter program. +**Answer:** There is a [separate page](http://boxes.thomasjensen.com/docs/filters.html) explaining this. *Boxes* is mostly used as a filter program. ###Q. 2. I have compiled and installed boxes, but when I run it, I get an error message "input in flex scanner failed"! @@ -17,7 +17,7 @@ Note that you can also set the tab stop distance (== how many spaces per tab) us ###Q. 4. "Can't read file C:\TEMP\VIO44.TMP" when calling boxes from vim -**Answer:** On Windows, this error message may appear instead of a box when *boxes* is called from vim. This is not a problem of *boxes*. In fact, it's a misleading message from the vim editor which is supposed to tell you that *boxes* is not in your PATH. Solution: Copy *boxes.exe* and *boxes.cfg* to a directory which is in your PATH. (thanks Jeff Lanzarotta, 05-Jul-00) +**Answer:** On Windows, this error message may appear instead of a box when *boxes* is called from vim. This is not a problem of *boxes*. In fact, it's a misleading message from the vim editor which is supposed to tell you that *boxes* is not in your PATH. Solution: Copy *boxes.exe* and *boxes.cfg* to a directory which is in your PATH. (thanks *Jeff Lanzarotta*, 05-Jul-00) ###Q. 5. Compilation