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:31:58 +0100 Message-ID: References: <87k3dte17j.fsf@fleche.redhat.com> <83r47yek5b.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2478e56b1a904f0a69e97 X-Trace: ger.gmane.org 1390498331 11572 80.91.229.3 (23 Jan 2014 17:32:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 23 Jan 2014 17:32:11 +0000 (UTC) Cc: tromey@redhat.com, monnier@iro.umontreal.ca, 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:32:18 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 1W6O8Y-0001bc-9h for ged-emacs-devel@m.gmane.org; Thu, 23 Jan 2014 18:32:18 +0100 Original-Received: from localhost ([::1]:42526 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6O8X-000570-Uf for ged-emacs-devel@m.gmane.org; Thu, 23 Jan 2014 12:32:17 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44732) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6O8O-00055z-Q4 for emacs-devel@gnu.org; Thu, 23 Jan 2014 12:32:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W6O8K-0007vL-5l for emacs-devel@gnu.org; Thu, 23 Jan 2014 12:32:08 -0500 Original-Received: from mail-qc0-x231.google.com ([2607:f8b0:400d:c01::231]:61776) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6O8F-0007rn-1b; Thu, 23 Jan 2014 12:31:59 -0500 Original-Received: by mail-qc0-f177.google.com with SMTP id i8so2848719qcq.36 for ; Thu, 23 Jan 2014 09:31:58 -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=KjS5M84QQbAqVTgn+fDXw0EPULy4xDNwAYqgVo1NxRo=; b=AQzfI0EEiJOyA00pqiy6tZbhmSt2Jsg5l8PeKP84gQyzhsegNGIwRC/EK++yuGdGqr 4UXGpdUPSpzL7JeJSVUvHHU6j8Y5Cft1pYYKxZNmIeYy+Nn+w+LbG4xUjN0k3GEIiA2m KBDCuy7uCf/kchdst+tTZ6hiF2TkfEdIOnkjtL/qM1ljUOmPW3aDyxQ/AiWm9/KpNqrq SxMuFSQa3tUAZaGmfBHWsK+pvEOFrmgh/isq6XWZW08CQgRQjauJ80N1pyO5jXzsUHnA E1GUycvcXvmj30ZdN9fL5h1OUIVveCVm6tzp4q5LMSAv/bx9vDx8NchLbRgBrxYoTccz 9YLA== X-Received: by 10.224.8.72 with SMTP id g8mr13372394qag.83.1390498318560; Thu, 23 Jan 2014 09:31:58 -0800 (PST) Original-Received: by 10.224.207.73 with HTTP; Thu, 23 Jan 2014 09:31:58 -0800 (PST) Original-Received: by 10.224.207.73 with HTTP; Thu, 23 Jan 2014 09:31:58 -0800 (PST) In-Reply-To: <83r47yek5b.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400d:c01::231 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:168968 Archived-At: --001a11c2478e56b1a904f0a69e97 Content-Type: text/plain; charset=UTF-8 Am 23.01.2014 17:29 schrieb "Eli Zaretskii" : > > > From: Sebastian Wiesner > > Date: Thu, 23 Jan 2014 15:24:14 +0100 > > Cc: Tom Tromey , Emacs-Devel devel < emacs-devel@gnu.org> > > > > > > I cannot see how *not* calling "message_with_string" in "write_region" > > could affect anything negatively. Especially in a non-interactive > > session, where "message_with_string" effectively comes down to > > "fprintf". > > Imagine some situation where this output is caught and parsed, for > example. > > In general, given behavior that is old enough, you can be sure that > someone, somewhere relies on it. I don't think it is my task to care for anyone, anywhere. If there is a concrete use case for these messages, fine, then we can try to find a good solution for either party involved, but we can't reasonably discuss about "virtual" use cases. --001a11c2478e56b1a904f0a69e97 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Am 23.01.2014 17:29 schrieb "Eli Zaretskii" <eliz@gnu.org>:
>
> > From: Sebastian Wiesner <lunaryorn@gmail.com>
> > Date: Thu, 23 Jan 2014 15:24:14 +0100
> > Cc: Tom Tromey <tromey@re= dhat.com>, Emacs-Devel devel <emacs-devel@gnu.org>
> >
> >
> > I cannot see how *not* calling "message_with_string" in= "write_region"
> > could affect anything negatively. =C2=A0Especially in a non-inter= active
> > session, where "message_with_string" effectively comes = down to
> > "fprintf".
>
> Imagine some situation where this output is caught and parsed, for
> example.
>
> In general, given behavior that is old enough, you can be sure that > someone, somewhere relies on it.

I don't think it is my task to care for anyone, anywhere= .=C2=A0

If there is a concrete use case for these messages, fine, th= en we can try to find a good solution for either party involved, but we can= 't reasonably discuss about "virtual" use cases.

--001a11c2478e56b1a904f0a69e97--