On Fri, 03 Jun 2011 15:38:29 -0700, Carl Worth wrote:
> commit d5b4d950245605b84c56ce991fa3c59a073a70e5
> Author: Jameson Graef Rollins
> Date: Sat May 28 14:52:00 2011 -0700
>
> show: Avoid inadvertently closing stdout
>
> GMime has a nasty habit of taking ownership by default of
On Fri, 03 Jun 2011 14:26:48 -0700, Jameson Graef Rollins
wrote:
> Well actually it's only meant to sound like the committer doesn't
> understand the problem!
Heh, OK.
> > I'd like to investigate this more. Perhaps with a test case?
>
> The current tests are how I found the problem! Without t
On Fri, 03 Jun 2011 12:56:50 -0700, Carl Worth wrote:
> Otherwise, the patches up to this point in the thread have all either
> been pushed or I've asked for some additional information (perhaps
> that's just this patch and the "old style fcc dirs" patch?).
Great! That's really great news, Carl.
On Fri, 03 Jun 2011 12:56:50 -0700, Carl Worth wrote:
> On Sat, 28 May 2011 14:52:00 -0700, Jameson Graef Rollins
> wrote:
> > The declaration of the GMimeStream pointer to stdout in
> > format_part_content_text was somehow preventing subsequent printf
> > calls from outputting to stdout if the
On Sat, 28 May 2011 14:52:00 -0700, Jameson Graef Rollins
wrote:
> The declaration of the GMimeStream pointer to stdout in
> format_part_content_text was somehow preventing subsequent printf
> calls from outputting to stdout if the output was redirected to a
> file. Scoping the declaration to th