What about *nix???

[Kenneth Brody]

John Esak wrote:
> 
> Okay, now you've done it.... I've just read the README and found a good
> thing.
> 
> It kind of proves the old adage "All good things come to those who wait."
> 
> 
> (Windows) #1016
>     On Windows, ddefine did not allow you to create or access files with
>     a dot in the filename.
> 
> 
> 
> So, that's nice.... But what about Unix? 

*nix filePro has always allowed a dot in filenames.  The problem came when 
people xfered their dot-containing files from *nix to Windows, and ddefine 
would reject the name.

> Now, I have some documentation
> somewhere that will show I sent you this problem back in 1994. :-)  I was
> trying to create a secret file to hold the resin prices for the plastics at
> nexus, and ddefine would not let me make it.  I just tried on a Linux system
> and lo and behold, it let me build a new file called ".resin"!  Yay!  *clerk
> will let me into the file from the command line! Yay!  But, :-( ddefine, nor
> any of the other creation programs, nor any of the runtime  programs will
> let me access the file once it's been created.  Has this been addressed in
> the 1016 fix?  I don't have the 5.6.10 loaded on a Windows system to try
> it... And since the fix only lists Windows specifically, could it be you
> think you fixed this back when I reported the Unix problem?  Should I send
> this in as a add-on to the original bug?

Well, you did say you wanted the file to be "secret".  :-)

The list of filenames that filePro presents to the user do not include files 
that start with a dot, as is *nix tradition.  (I could get picky and say 
that the fix says "files with a dot _in_ the filename", and not "at the 
start of the filename", but I won't.  In any case, what you are describing 
is a distinct issue from the fix.)

You can always set PFNAME=.resin if you need to handle this scenario.

> Actually, I think there really isn't any major bug, but probably just an
> oversite in the LISTBOX() being used to display the available files and it
> possibly using a system call that by default doesn't show filenames starting
> with a ".".  That would be an easy thing to fix, wouldn't it?  

Well, then your file wouldn't be secret anymore.  Unless you are saying that 
  (some?) creation programs shouldn't filter those out.

[...]

-- 
Kenneth Brody