Date: Sun, 2 Feb 2003 16:20:42 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: DJGPP developers <djgpp-workers AT delorie DOT com>
Subject: Re: symify docs
In-Reply-To: <10302020712.AA22570@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1030202161715.26481A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 2 Feb 2003, Charles Sandmann wrote:

> (I may get OK at this yet):

You are almost there ;-)

> Specify source path as @var{source-path} to find source files used to
> build this image.  The source path can also be set as an environment 
> variable @var{FSDBPATH}, but the command line option will override the

Environment variables should have the @env markup.  @var is not for 
variables, but for things that stand for something else.  E.g., 
@var{source-path} stand for the path that FSDB should search for source 
files.  By contrast, FSDBPATH is a name of a variable that stands for 
itself.  So @var is inappropriate for it.  The same is true for `errno' 
(another ``popular'' mistake)--not that you used it in this case.