delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mailnull set sender to djgpp-workers-bounces using -f |
From: | sandmann AT clio DOT rice DOT edu (Charles Sandmann) |
Message-Id: | <10203071641.AA17682@clio.rice.edu> |
Subject: | Re: Proposed readme.1st changes |
To: | djgpp-workers AT delorie DOT com |
Date: | Thu, 7 Mar 2002 10:41:35 -0600 (CST) |
In-Reply-To: | <200203071259.NAA21612@lws256.lu.erisoft.se> from "Martin Stromberg" at Mar 07, 2002 01:59:40 PM |
X-Mailer: | ELM [version 2.5 PL2] |
Mime-Version: | 1.0 |
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 |
> > ! subdirectories: it will not work! See the FAQ for more details.) Do > > ! not use a long directory name or one with spaces or special characters. > > Isn't "special character" a little vague. Perhaps nonalphanumeric is > better? Most nonalphanumerics are legal. Special is: +,;=[] as far as I know, but maybe others break it. The goal here is to get people to think twice about not using the recommended default - based on some of the newsgroup questions I've seen over the last few years. Vague in this case isn't always bad - we're trying to keep it short and warn you of things to do (or not do). The true definition of "special character" is anything that causes DJGPP not to work on your system :-) For the newbie "long directory name" probably doesn't make much sense, and the entire discussion of 8.3 versus long names and LFN TSR for NT is pretty thick too. The goal once again, was awareness - to get someone to download the package and read the docs, or to consult the FAQ, or to ask on the newsgroup. A real humbling experience is to have to sit in a usability lab while someone with little experience reads your docs and tries to install the software :-(
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |