Date: Thu, 13 Sep 2007 12:38:43 -0700 From: "Kurt Buff" <kurt.buff@gmail.com> To: "Jeffrey Goldberg" <jeffrey@goldmark.org> Cc: questions@freebsd.org Subject: Re: Scripting question Message-ID: <a9f4a3860709131238u18a48a48kbd06cfbc720d4e4d@mail.gmail.com> In-Reply-To: <13D9DDEB-5AC6-4E2C-93F3-40054A97E3C9@goldmark.org> References: <a9f4a3860709131016w54c12b6fy94fc2b0f286aea3d@mail.gmail.com> <20070913172001.GA78799@gizmo.acns.msu.edu> <a9f4a3860709131032q21bfefc2hf8d78cae53637576@mail.gmail.com> <20070913175510.GA78984@gizmo.acns.msu.edu> <a9f4a3860709131119h2d7589aej59587749bb1fa2ef@mail.gmail.com> <13D9DDEB-5AC6-4E2C-93F3-40054A97E3C9@goldmark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/13/07, Jeffrey Goldberg <jeffrey@goldmark.org> wrote: > On Sep 13, 2007, at 1:19 PM, Kurt Buff wrote: > > > I think I may have a better solution. The file I'm trying to massage > > has a predecessor - the non-unique lines are the result of a > > concatenation of two files. > > > > Silly me, it's better to 'grep -v' with the one file vs. the second > > rather than trying to merge, sort and further massage the result. The > > fix will be to use sed against the first file to remove the ' NO', > > thus providing a clean argument for grepping the other file. > > Instead of grep -v take a look at comm. > > -j Interesting! I just looked at the man page, and while I don't think it it's going to be directly useful (or I'm just not reading the page correctly), it's a new utility to me - I'll keep it in mind for other things. Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a9f4a3860709131238u18a48a48kbd06cfbc720d4e4d>