From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5997b4b7b514f689 X-Google-Attributes: gid103376,public From: mheaney@ni.net (Matthew Heaney) Subject: Re: Reading a line of arbitrary length Date: 1997/02/15 Message-ID: #1/1 X-Deja-AN: 219121076 References: <5ds40o$rpo@fg70.rz.uni-karlsruhe.de> <01bc18d6$41e00680$188c71a5@dhoossr.iquest.com> <330319F1.41C67EA6@innocon.com> <5dv7ea$epi$1@news.iag.net> <33033173.6EC9@mds.lmco.com> Content-Type: text/plain; charset=ISO-8859-1 Organization: Estormza Software Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1997-02-15T00:00:00+00:00 List-Id: In article <33033173.6EC9@mds.lmco.com>, rex.r.reges@lmco.com wrote: >The problem with command line input on Unix is that it does >require arbitrarily long string inputs. For example, when >the command "grep -i find_me *" is issued, the asterisk >must be replaced by the names of all of the files in the current >directory before the command is passed to grep. But isn't that what the command xargs is used for? -------------------------------------------------------------------- Matthew Heaney Software Development Consultant (818) 985-1271