 | | Re: Testing long filenames was Re: Unofficial directory (with non-standard name lenght)?
|
|
(...) (URL) Here's> the output on XP. ROSCO (18 years ago, 2-Mar-07, to lugnet.cad.dev, FTX)
|
| |
| | Re: Testing long filenames was Re: Unofficial directory (with non-standard name lenght)?
|
|
(...) Well, I made a small program in Delphi 7 that lists the command line parameters, drag and dropped a file named "LongFileName.dat" in it, and here is the surprising result: (URL) (Running on a Win98SE PC.) So I think long file names still has (...) (18 years ago, 2-Mar-07, to lugnet.cad.dev, FTX)
|
| |
| | Re: Unofficial directory (with non-standard name lenght)? (Was: LDView 3.1 on Mac OS X!)
|
|
(...) The only character either Linux or Mac OS X is allergic to is '/'. Spaces are perfectly acceptable under both. One need only take care that any paths fed to the shell are properly escaped. Ideally anybody writing shell scripts or system() (...) (18 years ago, 2-Mar-07, to lugnet.cad.dev, FTX)
|
| |
| | Re: Unofficial directory (with non-standard name lenght)? (Was: LDView 3.1 on Mac OS X!)
|
|
(...) With tongue slightly in cheek, I believe it is time to accept the technological advancements of 1984. If DOS wasn't obsolete the day it was written, it definitely was within a few years. DOS filenames tend to be inscrutable, and there just (...) (18 years ago, 2-Mar-07, to lugnet.cad.dev, FTX)
|
| |
| | Re: Unofficial directory (with non-standard name lenght)? (Was: LDView 3.1 on Mac OS X!)
|
|
(...) First of all, I agree that we should avoid using space in filenames for all official stuff. It's just too problematic. However, that's not a reason to forbid the use of long filenames in general. The thing is, any program that doesn't support (...) (18 years ago, 1-Mar-07, to lugnet.cad.dev, FTX)
|
| |
| | Testing long filenames was Re: Unofficial directory (with non-standard name lenght)?
|
|
(...) And sorry to reply to myself... Could people using older operating systems test this? I'm happy to maintain the status quo if there are problems but if no-one finds problems then I think we make the majority suffer for something that isn't (...) (18 years ago, 1-Mar-07, to lugnet.cad.dev, FTX)
|
| |
| | Re: Unofficial directory (with non-standard name lenght)? (Was: LDView 3.1 on Mac OS X!)
|
|
(...) I'm not sure about 98 and its ilk but I've never had any problems with long filenames in XP for l3p (and possible other command lines although I can't remember any off hand). I would certainly recommend against using spaces in filenames as (...) (18 years ago, 1-Mar-07, to lugnet.cad.dev, FTX)
|
| |
| | Re: Unofficial directory (with non-standard name lenght)? (Was: LDView 3.1 on Mac OS X!)
|
|
(...) It it really so? We still use renderers and utilities that have command line inputs, and I don't know but I have a strong feeling that long names may cause problems like "Unofficial" turs into "Unoffi~1" followed by path not found errors. And (...) (18 years ago, 1-Mar-07, to lugnet.cad.dev, FTX)
|
| |
| | Re: Unofficial directory (with non-standard name lenght)? (Was: LDView 3.1 on Mac OS X!)
|
|
--snip-- (...) Personally I'm against maintaining it. It forces us into strange naming conventions for something which probably affects no users of the software. Tim (18 years ago, 28-Feb-07, to lugnet.cad.dev, FTX)
|
| |
| | Unofficial directory (with non-standard name lenght)? (Was: LDView 3.1 on Mac OS X!)
|
|
(...) So far, we have maintained the old DOS convention of max. 8 chars and no SPACE used in folder names. I realize that fewer and fewer programs and utils are made in DOS evironments, maybe I'm the only to still make quick 'n' dirty programs in (...) (18 years ago, 28-Feb-07, to lugnet.cad.dev.mac, lugnet.cad.dev, FTX)
|
