[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Various MiNT questions
- To: firstname.lastname@example.org (troy)
- Subject: Re: Various MiNT questions
- From: email@example.com (Michael Hohmuth)
- Date: Wed, 10 Aug 1994 01:43:32 +0200 (MET DST)
- Cc: firstname.lastname@example.org
- In-reply-to: <"8022 Mon Aug 8 15:37:12 1994"@bnr.ca> from "troy" at Aug 8, 94 03:34:00 pm
- Organization: Dept. of Computer Science, TU Dresden, Germany
> Maybe I misunderstood the README file, but it souned like this to me:
> If you #undef DOSFS, then tcsh would use the dot files, but _it would not know
> how to access files on TOS partitions._ Leaving DOSFS defined _would_ allow
> access to TOS partitions, but as a side effect used an 8.3 scheme for resource
> files since you cannot use dot files on a TOS partitions.
Nope. If you #undef DOSFS, `tcsh' just can't understand names like
"c:\foo.goo". You could still access this file as "/c/foo.goo".
As I'm not a native speaker, I'd appreciate your comments on the
documentation I write, especially on where it is ambiguous.
Here's the relevant part from the README.ST:
o If you define DOSFS, tcsh's builtins will support DOS file
names with drive specifications (like "a:") and backslashes
(which have to be escaped, like "\\"). Also, tcsh will use
DOS compatible names for its configuration files
(`login.csh' instead of `.login', for instance; see above
for a complete list of affected file names).