Ethereal-dev: Re: [ethereal-dev] What should Ethereal do for command-line option errors?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Nathan Neulinger <nneul@xxxxxxx>
Date: Tue, 07 Dec 1999 07:49:45 -0600
Stefan `Sec` Zehl wrote:
> 
> On Mon, Dec 06, 1999 at 11:18:59PM -0800, Guy Harris wrote:
> > If it's run with a bad command-line option, e.g. an invalid one ("-z"),
> > or one that's supposed to have an argument ("-m") but isn't given one,
> > or one that's supported only if Ethereal is built with "libpcap" ("-k"),
> > should it pop up a window, or should it just print a message and exit?
> 
> [...]
> 
> Do it just like ssh-add does. Use stdout if there is one and it's not
> /dev/null. Otherwise use X :-)

Actually, that's not such a good idea. Maybe checking if stdout is a tty
would be sufficient, but if you do it just checking if it's there is bad
practice, cause almost everything in X will write to xsession-errors or
similar. 

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@xxxxxxx
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216