Path: utzoo!attcan!uunet!decwrl!pa.dec.com!shlump.nac.dec.com!lemans.dec.com!lemans.det.dec.com!libove From: libove@libove.det.dec.com (Jay Vassos-Libove) Newsgroups: comp.unix.sysv386 Subject: Re: 14 character limitation in filenames Message-ID: Date: 1 Feb 91 16:42:17 GMT References: <290@sps.com> <20711@hydra.gatech.EDU> <1991Feb1.003532.15719@NCoast.ORG> Sender: news@lemans.dec.com Followup-To: comp.unix.sysv386 Organization: Digital Equipment Corporation, Detroit Ultrix Resource Center Lines: 18 In-reply-to: allbery@NCoast.ORG's message of 1 Feb 91 00:35:32 GMT Actually, though Brandon complains that long filenames are a pain to type, a good shell can take care of that... I happily swipe fifty and more character filenames in to a command line by punching escape every now and then and letting my ksh or enhanced csh or enchanced sh find the file on disk and complete the filename, or by punching ^D and having the shell print out possible completions for me. Besides, just because you can have longer filenames doesn't mean you have to use them. Why turn down functionality? I hate it when bison tries to create ">8 character filename".output files and fails under SysVr3, and when patch tries to generate "14 character filename"# or ~ and fails... etc. -- Jay Vassos-Libove libove@libove.det.dec.com Digital Equipment Corporation decwrl!libove.det.dec.com!libove Detroit ACT/Ultrix Resource Center Opinions? They're mine, mine, all mine! Farmington Hills, Michigan and D.E.C. Can't have 'em!