[2689] in SIPB bug reports
dvips file.dvi | lpr -Pprintername
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Mon Apr 6 21:33:46 1992
Date: Mon, 6 Apr 92 21:33:14 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: jefft@Athena.MIT.EDU
Cc: bug-sipb@Athena.MIT.EDU
In-Reply-To: Jeff Tang's message of Mon, 06 Apr 92 19:15:13 EDT <9204062315.AA14504@neptune.MIT.EDU>
From: Jeff Tang <jefft@Athena.MIT.EDU>
Date: Mon, 06 Apr 92 19:15:13 EDT
Sender: jefft@Athena.MIT.EDU
Lots of people try and use dvips incorrectly like this:
dvips file.dvi | lpr -Pprintername
Perhaps it would be useful if dvips printed some sort of warning if it's
output is piped through something. I can't think of a good reason to
actually use the usage, so it probably wouldn't hurt anything.
It is impossible for a program to tell reliably "if it's [sic] output
is piped through something," especially when the program can be run
through a shell script run in the background and connected to no tty.
User education is the answer, not gross hacks to a program we don't
maintain.
Incidentally, there *is* a reason to redirect output "dvips file.dvi >
/dev/null".
jik
