Article View: comp.unix.programmer
Article #898Re: File "type"
From: Paul Chamberlain
Date: Mon, 24 Sep 1990 15:35
Date: Mon, 24 Sep 1990 15:35
12 lines
1273 bytes
1273 bytes
In article <171@alchemy.UUCP> bbs@alchemy.UUCP (BBS Administration) writes: > Could someone explain how the command "file" works? Specifically, I am >writing a program that allows users to navigate their $HOME directory and ... I agree that reading in the first block and making basic sanity checks is probably the best thing to do to verify the sanity of editing it. However, if you desire any more detail, I would seriously consider reading the output of the "file" command itself. Or if you have some deep reason to avoid that, get one of the PD implementations of "file" and suck it into your source. Paul Chamberlain | I do NOT represent IBM tif@doorstop, sc30661@ausvm6 512/838-7008 | ...!cs.utexas.edu!ibmaus!auschs!doorstop.austin.ibm.com!tif
Technical Details
Message-ID:
<3642@awdprime.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!mailrus!cs.utexas.edu!romp!auschs!awdprime!doorstop.austin.ibm.com!tifReferences:
<171@alchemy.UUCP> <13114@june.cs.washington.edu> <12141@chaph.usc.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!mailrus!cs.utexas.edu!romp!auschs!awdprime!doorstop.austin.ibm.com!tif From: tif@doorstop.austin.ibm.com (Paul Chamberlain) Newsgroups: comp.unix.programmer Subject: Re: File "type" Message-ID: <3642@awdprime.UUCP> Date: 24 Sep 90 15:35:21 GMT References: <171@alchemy.UUCP> <13114@june.cs.washington.edu> <12141@chaph.usc.edu> Sender: news@awdprime.UUCP Reply-To: tif@doorstop.austin.ibm.com (Paul Chamberlain) Organization: IBM AWD, Austin, TX Lines: 12