From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Sebastian Wiesner Newsgroups: gmane.emacs.devel Subject: Re: Inhibit "Wrote foo" from write-region Date: Thu, 23 Jan 2014 18:37:09 +0100 Message-ID: References: <87k3dte17j.fsf@fleche.redhat.com> <83siseekd4.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2989ce3ad6604f0a6b023 X-Trace: ger.gmane.org 1390498647 15133 80.91.229.3 (23 Jan 2014 17:37:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 23 Jan 2014 17:37:27 +0000 (UTC) Cc: tromey@redhat.com, Stefan Monnier , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 23 18:37:29 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1W6ODY-0003oh-45 for ged-emacs-devel@m.gmane.org; Thu, 23 Jan 2014 18:37:28 +0100 Original-Received: from localhost ([::1]:42539 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6ODX-0006su-MA for ged-emacs-devel@m.gmane.org; Thu, 23 Jan 2014 12:37:27 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46279) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6ODQ-0006sV-Ho for emacs-devel@gnu.org; Thu, 23 Jan 2014 12:37:25 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W6ODL-0001Bl-LA for emacs-devel@gnu.org; Thu, 23 Jan 2014 12:37:20 -0500 Original-Received: from mail-qa0-x234.google.com ([2607:f8b0:400d:c00::234]:35252) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6ODG-0001Ai-9R; Thu, 23 Jan 2014 12:37:10 -0500 Original-Received: by mail-qa0-f52.google.com with SMTP id j15so2559740qaq.39 for ; Thu, 23 Jan 2014 09:37:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Kjv4g2pWN3VaqVSd/mqoBhM1XNHnxUWCf+pqrCyPO0A=; b=iDCemVWbEKdE4oWSG9jFp6OlT0bJ1EGPSYKc2V5Rxts3Kp1OmznjkHgss0EMRvFZQq JfcAGzdb0z7lYVgCZxiCS090UsqwiQO22e71enYFK8HZnciYxYv45Gc5DYo7TNzc/Ecl 6HbX8JlFkvE0q97FFZxuZDgBeXafNCYX56JQMwFRucGnqEbeHCzlj1D75ifzJGp2rrSB erAHt47zioNxLXjD4ZpYyVSNZ9rFs1RlQdGjZkeN/0cGoeLJD1UzT1c+a6MbvcbRMIXx lA5jgDt1zib7XxTP8sGHbmkN/hhlc9BJ+01eYQ8ulQinga9pCfEwn4bvFJp4flS10gR8 Xx6g== X-Received: by 10.224.47.1 with SMTP id l1mr736096qaf.67.1390498629789; Thu, 23 Jan 2014 09:37:09 -0800 (PST) Original-Received: by 10.224.207.73 with HTTP; Thu, 23 Jan 2014 09:37:09 -0800 (PST) Original-Received: by 10.224.207.73 with HTTP; Thu, 23 Jan 2014 09:37:09 -0800 (PST) In-Reply-To: <83siseekd4.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400d:c00::234 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:168969 Archived-At: --001a11c2989ce3ad6604f0a6b023 Content-Type: text/plain; charset=UTF-8 Am 23.01.2014 17:24 schrieb "Eli Zaretskii" : > > > From: Stefan Monnier > > Date: Thu, 23 Jan 2014 08:50:20 -0500 > > Cc: Tom Tromey , 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? --001a11c2989ce3ad6604f0a6b023 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

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@re= dhat.com>, Emacs-Devel devel <emacs-devel@gnu.org>
> >
> > > I presume, there is little chance to change this behaviour f= or
> > > noninteractive use?
> >
> > Definitely not for 24.4.
> >
> > Afterwards, someone could try and look at the issue in more detai= l, but
> > it's risky, since it's a fairly low-level primitive calle= d from many
> > different packages. =C2=A0We'd have to go and check how all t= hese 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?!=C2=A0 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 me= ssages 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?

--001a11c2989ce3ad6604f0a6b023--