Redirecting stderr to the output window probably could be done, but would need to be carefully considered.
* What about those that occur before the output window is created?
* What about critical errors from Gtk / Glib? Should they also go
to the output window? If so, it could leed to looping.
* There's an open feature request to allow more than one output window.
Which one would get the stderr?
However, one thing we really should do, is to generate a warning if
a procedure iterates less cases than expected.
J'
On Mon, Aug 22, 2011 at 10:01:01AM -0700, Ben Pfaff wrote:
John Darrington <j...@darrington.wattle.id.au> writes:
> Certain low-level error messages get sent to the terminal, but not
> the gui. Any such messages might give us a clue to the problem,
> and how to fix it.
We probably should add support for a log file, to capture this
kind of output. (Maybe we should write these messages to the
existing journal, as comments?)
--
Ben Pfaff
http://benpfaff.org
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://pgp.mit.edu or any PGP keyserver for public key.
signature.asc
Description: Digital signature
_______________________________________________ pspp-dev mailing list pspp-dev@gnu.org https://lists.gnu.org/mailman/listinfo/pspp-dev
