On Saturday 10 November 2007 13:48, Ben Kevan wrote: > > This is the idiomatic (and easier to type and of lower overhead) > > way to accomplish what you're suggesting: > > > > % grep NoLogo /etc/X11/xorg.conf > > > > > > Randall Schulz > > LOL, Thanks Randall.. > > I know the method you provided is less overhead but sometimes to me > the piping helps me visually see the difference in commands..
Well, that's fine, but the point is that only one real command is essential to accomplish the task you were describing. Arbitrarily and unnecessarily complicating the command you use to achieve any given end doesn't really help, does it? > I know horrible practice but I am not a Bash scripter etc. I live and breath BASH scripting, though I continue to rely on the documentation for many of the less common capabilities. The syntax is pretty funky and overly baroque, if you ask me, but for a lot of things, it gets the job done and is as universal as anything in the Unix / Linux world. By the way, another equivalent to your command and my replacement for it is this: % grep NoLogo </etc/X11/xorg.conf In this case, the shell opens the file and if there's a problem doing so (file non-existent or unreadable, e.g.), the shell gives you the diagnostic without even invoking the actual command. > ... > > Ben Randall Schulz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
