Am 23.01.2014 17:24 schrieb "Eli Zaretskii" <eliz@gnu.org>:
>
> > From: Stefan Monnier <monnier@iro.umontreal.ca>
> > Date: Thu, 23 Jan 2014 08:50:20 -0500
> > Cc: Tom Tromey <tromey@redhat.com>, Emacs-Devel devel <emacs-devel@gnu.org>
> >
> > > I presume, there is little chance to change this behaviour for
> > > noninteractive use?
> >
> > Definitely not for 24.4.
> >
> > Afterwards, someone could try and look at the issue in more detail, but
> > it's risky, since it's a fairly low-level primitive called from many
> > different packages.  We'd have to go and check how all these calls would
> > be affected.
>
> I, for one, am accustomed to see these messages while Emacs is being
> built: in a highly parallel build that is sometimes the only practical
> way of knowing whether some part of the build succeeded or not.

How do you do that?!  Do you really read *all* messages being printed while building?!

I presume that just testing for the existence of interesting files (e.g. good old "find") isn't an option?

> So, if 'write-region' stops outputting these messages in
> non-interactive uses, there should be a way to get the current
> behavior back.

Isn't that the job of the build system rather?