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: Fri, 24 Jan 2014 21:14:38 +0100 Message-ID: References: <87k3dte17j.fsf@fleche.redhat.com> <83r47yek5b.fsf@gnu.org> <83ob32efrq.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2478ef27d9704f0bd0174 X-Trace: ger.gmane.org 1390594483 15321 80.91.229.3 (24 Jan 2014 20:14:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 24 Jan 2014 20:14:43 +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 Fri Jan 24 21:14:49 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 1W6n9M-0000a3-Kv for ged-emacs-devel@m.gmane.org; Fri, 24 Jan 2014 21:14:48 +0100 Original-Received: from localhost ([::1]:48734 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6n9M-0000S3-7G for ged-emacs-devel@m.gmane.org; Fri, 24 Jan 2014 15:14:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36898) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6n9H-0000QN-J3 for emacs-devel@gnu.org; Fri, 24 Jan 2014 15:14:45 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W6n9G-00062l-1y for emacs-devel@gnu.org; Fri, 24 Jan 2014 15:14:43 -0500 Original-Received: from mail-qc0-x22a.google.com ([2607:f8b0:400d:c01::22a]:62450) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6n9E-00062B-Df; Fri, 24 Jan 2014 15:14:40 -0500 Original-Received: by mail-qc0-f170.google.com with SMTP id e9so5149177qcy.29 for ; Fri, 24 Jan 2014 12:14:39 -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=Lo34+aVoF6/LgseOD91d+aYRUBLwgT1Fi0L9olREtJk=; b=v7OD4wFCBFkxG7fjG+Am4UQIZ79yUt0DkyASFFAFpg1NemhFSnCo5IAAQoQQ9K6SJl rj8Yni/DDM+fPBbkO5zObj6fyamgqc//PkXq0UnMMWgdJDOF95jw1u2X0B5NgZiCxWx9 jRUXxjxd+iCTwNoFKTR37c3B8yrbwEfVXkyfoKyna9FKq1j9Kgv3PAXC4nITdrpM11YC SDhZkJfMTM7IqTx+VvdqL+MTP4U4zib3u56mFbzjADTqauecHjQ2iJwWyvjjW00YEz4a T2JBiNonVW6DJfbz+dQH/GBFesVIMNteDr1LzASe7XzIEUYEw9sYpCZW9olo7BQlrcef vj7w== X-Received: by 10.224.8.72 with SMTP id g8mr23355361qag.83.1390594478995; Fri, 24 Jan 2014 12:14:38 -0800 (PST) Original-Received: by 10.224.207.73 with HTTP; Fri, 24 Jan 2014 12:14:38 -0800 (PST) Original-Received: by 10.224.207.73 with HTTP; Fri, 24 Jan 2014 12:14:38 -0800 (PST) In-Reply-To: <83ob32efrq.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::22a 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:169027 Archived-At: --001a11c2478ef27d9704f0bd0174 Content-Type: text/plain; charset=UTF-8 Am 23.01.2014 19:04 schrieb "Eli Zaretskii" : > > > Date: Thu, 23 Jan 2014 18:31:58 +0100 > > From: Sebastian Wiesner > > Cc: tromey@redhat.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org > > > > > 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. > > Why not? Backward incompatibility is one of the worst traits in > software, IMO. Not undoing or fixing bad design decisions from the past is another one, IMHO. > > 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. > > I just gave you one concrete use case, above. Which I replied to with concrete questions, with the intent to, well, "find a good solution for either party involved"... --001a11c2478ef27d9704f0bd0174 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Am 23.01.2014 19:04 schrieb "Eli Zaretskii" <eliz@gnu.org>:
>
> > Date: Thu, 23 Jan 2014 18:31:58 +0100
> > From: Sebastian Wiesner <lunaryorn@gmail.com>
> > Cc: tromey@redhat.com, <= a href=3D"mailto:monnier@iro.umontreal.ca">monnier@iro.umontreal.ca, emacs-devel@gnu.org
> >
> > > Imagine some situation where this output is caught and parse= d, for
> > > example.
> > >
> > > In general, given behavior that is old enough, you can be su= re that
> > > someone, somewhere relies on it.
> >
> > I don't think it is my task to care for anyone, anywhere.
>
> Why not? =C2=A0Backward incompatibility is one of the worst traits in<= br> > software, IMO.

Not undoing or fixing bad design decisions from the past is = another one, IMHO.

> > 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.
>
> I just gave you one concrete use case, above.

Which I replied to with concrete questions, with the intent = to, well, "find a good solution for either party involved"...

--001a11c2478ef27d9704f0bd0174--