Re: Huge Text Files

[Ben Pfaff]

John Darrington <address@hidden> writes:

> 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?

I agree with those caveats, but it's not what I was suggesting.
I was suggesting to write them to a disk file, so that users
could look at them in a separate program or mail them to
developers for debugging help

> However, one thing we really should do, is to generate a warning if
> a procedure iterates less cases than expected.

Yes, I agree.

> 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 
>      http://benpfaff.org

-- 
Ben Pfaff 
http://benpfaff.org