|Re: [AD] Hashes bite back|
[ Thread Index |
| More lists.liballeg.org/allegro-developers Archives
> On January 1, 2004 01:14 pm, Grzegorz Adam Hankiewicz wrote:
>> On 2004-01-01, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
>> > > > The problem is - filenames in linux can contain any character
>> > >
>> > > Not really, path separators, possibly \0 depending on
>> > > implementation, maybe something else...
>> > just escape the special char, and you can use it. :) Otherwise, even
>> non ascii works... Though with my current settings, it shows up as
>> ascii ;) (garbage...)
>> Are you sure?
> pretty sure.. Just not sure how easy it is to create them via the
> shell.. I've had some funky file names come out of "rename" ;) Could be
Yep, you're wrong. Unix filenames really can't contain '/' or NUL.
Everything else is permissible. ("ls -l|wc" is buggy.)
I'm not really sure what to do about the hash problem though. The option
is probably acceptable, but not very nice.