Bug#341906: [Pkg-octave-devel] Bug#341906: octave prints copyright/debugging information on stdout instead of stderr

[Frederik Eaton]

On Mon, Jan 09, 2006 at 11:40:10AM -0500, John W. Eaton wrote:
> On  9-Jan-2006, Frederik Eaton wrote:
> 
> | On Mon, Jan 09, 2006 at 10:33:40AM +0100, Rafael Laboissiere wrote:
> | > * Frederik Eaton <frederik at a5.repetae.net> [2006-01-09 03:07]:
> | > 
> | > > You're right, mysql seems to print to stdout, while "perl -d" writes
> | > > directly to the terminal. In any case, I don't see a reason not to
> | > > adopt my suggestion.
> | > > 
> | > > The convincing argument is that one typically wants to be able to have
> | > > rather strict control over what the output of a program is. When
> | > > 'stdout' gets cluttered with other messages, it loses its usefulness
> | > > very quickly.
> | > 
> | > Why doesn't the -q command option suit your needs?
> | 
> | One can only put so many options on the "#!" line, I think the limit
> | is 1. I could remember to put "-q" in every octave script, and
> | complain when I need to add another option and can't, but then, why
> | not have a sensible default?
> 
> Hi,
> 
> I think you already argued this point on the Octave mailing list, and
> I was not convinced that the change was needed.  Would it really be
> good to have the Debian package include a special patch for this
> change that was not a part of the upstream Octave distribution?
> 
> jwe

I don't remember where it was argued, I was just explaining my
thoughts to Rafael. I don't think that a special patch would be ideal,
no.

Frederik