[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Huge Text Files

From: John Darrington
Subject: Re: Huge Text Files
Date: Tue, 23 Aug 2011 17:00:50 +0000
User-agent: Mutt/1.5.18 (2008-05-17)

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.


On Mon, Aug 22, 2011 at 10:01:01AM -0700, Ben Pfaff wrote:
     John Darrington <address@hidden> 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

PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See or any PGP keyserver for public key.

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]