To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>,
        DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: Fetish.pm band-aid (Fileutils testsuite)
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010305093405 DOT 23825J AT is>
In-Reply-To: <Pine.SUN.3.91.1010305093405.23825J@is>
From: Jim Meyering <jim AT meyering DOT net>
Date: 06 Mar 2001 03:43:31 +0100
Message-ID: <urybsrf39d8.fsf@ixi.eng.ascend.com>
Lines: 26
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.0.99
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: Jim Meyering <meyering AT ascend DOT com>
Reply-To: djgpp-workers AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:

| On 4 Mar 2001, Jim Meyering wrote:
|
| > FYI, the quotes from _shell_quote are necessary for the file
| > names used in some of the tests because those names contain
| > meta-characters.
|
| As you probably know, Jim, most meta-characters will not work on
| DOS/Windows because they are invalid in file names, even if quoted.
| I'm talking about characters from the set "*?:<>| (including the
| double quote).  Newlines are also not allowed, and forward and
| back-slashes are only allowed as directory separators, not as literal
| characters.  Plain DOS disallows a few more characters, such as + and
| [.

Thanks for explaining.
I think the only case is in tests/ls-2.  I used \a in a file
name to test how ls displays the file name with various options.

| If the tests you are talking about involve any of these, they are
| bound to fail with the DJGPP port, and we should devise a way to
| bypass those tests on DOS/Windows.  One possible way of bypassing them
| cleanly is to try to create a file with the offending character with
| some simple shell command, such `echo', and if that fails, you know
| not to run the test.