home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.shell
- Path: sparky!uunet!tekbspa!tekbspa!esh
- From: esh@lithium.tekbspa.com (Edward S. Hirgelt)
- Subject: Re: Where does the sugar go? (was Re: Sort problem )
- In-Reply-To: chip@eniac.seas.upenn.edu's message of 31 Jul 92 03:30:28 GMT
- Message-ID: <ESH.92Jul31101723@lithium.tekbspa.com>
- Sender: news@tss.com (USENET Network News)
- Organization: Direct Interfaces Corporation @ Teknekron
- References: <33pmg <1992Jul31.000822.13317@convex.com> <84902@netnews.upenn.edu>
- Date: Fri, 31 Jul 1992 18:17:23 GMT
- Lines: 26
-
-
- On 31 Jul 92 03:30:28 GMT,
- chip@eniac.seas.upenn.edu (Charles H. Buchholtz) said:
- Charles> Sender: news@netnews.upenn.edu
- Charles> Nntp-Posting-Host: eniac.seas.upenn.edu
-
- Charles> So, folks, what's the verdict? Output goes to stdout, preferably
- Charles> arranged in lines and fields for easy filtering. Error messages and
- Charles> diagnostics (abnormal stuff) goes to stderr. Where should the sugar
- Charles> go? stdout? /dev/tty? /dev/null? >&3?
-
- Actually, I think it should go to stdout as well. To be filterable, the
- headers and other `sugar' ought to disappear. The right answer (for the
- future) is that the command ought to have a flag to disable headers.
-
- You don't really want to route that to a different file descriptor
- because the command would then have to worry about synchronizing the two
- descriptors to keep the non-filtered output looking good. ps could use a
- -noheader flag or something that tells it to forget the header this
- time, I want to play with the output.
-
- Ed
- --
- Ed Hirgelt esh@tss.com
- Direct Interfaces Corporation
- San Jose, Ca.
-