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 10:35:17 +0100 Message-ID: References: <87k3dte17j.fsf@fleche.redhat.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1390469729 32540 80.91.229.3 (23 Jan 2014 09:35:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 23 Jan 2014 09:35:29 +0000 (UTC) Cc: Tom Tromey , Emacs-Devel devel To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 23 10:35:37 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 1W6GhF-0006pw-4Z for ged-emacs-devel@m.gmane.org; Thu, 23 Jan 2014 10:35:37 +0100 Original-Received: from localhost ([::1]:39673 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6GhE-0004rC-9h for ged-emacs-devel@m.gmane.org; Thu, 23 Jan 2014 04:35:36 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57818) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6Gh1-0004q9-8p for emacs-devel@gnu.org; Thu, 23 Jan 2014 04:35:24 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W6Gh0-0002YT-0s for emacs-devel@gnu.org; Thu, 23 Jan 2014 04:35:23 -0500 Original-Received: from mail-bk0-x235.google.com ([2a00:1450:4008:c01::235]:45403) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6Ggz-0002YI-PQ for emacs-devel@gnu.org; Thu, 23 Jan 2014 04:35:21 -0500 Original-Received: by mail-bk0-f53.google.com with SMTP id my13so262932bkb.12 for ; Thu, 23 Jan 2014 01:35:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version:content-type; bh=ZOisohHldEFxNXy8Vj0zBR5u+7S/meiNOiEhgBxUuKo=; b=EIUT/AYLC3o2i3Ra2ZGW1hlXzUapLGbk+Xw+o1Y7gi68bG7UeKJePaqh5hITZbkqFn TJ92/5q52X9OscB6RHNPER9YjLlqBCP9FmajonE3noYDxFt+erN4/ExDGIMVpuJB6SOM 8YjauasCLZlp7MPqzAUYIt1KvBtbQR3YTHshS5Czc6dhvYwHALYvvo3HNDRBBqFxmkeW kRa80q3hHlu769GCioVzoapGlpdfQPE25IHwfMPn9oTbXUp7+g36fvB5jddvHHVwhplv p0F2HyPAQ4yx652IHrq/+lapnClZkvZ38/gJ3znodwZyNp1vAoMnSg/TyC15H9AOAJGM gkyQ== X-Received: by 10.205.76.10 with SMTP id zc10mr947858bkb.43.1390469720584; Thu, 23 Jan 2014 01:35:20 -0800 (PST) Original-Received: from lunaryorn-air.fritz.box ([2001:a60:1110:c901:e858:f27a:b793:1d16]) by mx.google.com with ESMTPSA id np8sm8612835bkb.11.2014.01.23.01.35.18 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Jan 2014 01:35:19 -0800 (PST) User-agent: mu4e 0.9.9.6pre2; emacs 24.3.50.1 In-reply-to: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4008:c01::235 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:168941 Archived-At: monnier@iro.umontreal.ca writes: >> There is a typo ("ni" -> "nil"), and I don't exactly understand what the >> other changes unrelated to write-region are for. Other than that, looks >> good. > > Thanks, installed. > >> Just out of curiosity: What is the rationale behind these messages? >> Why does write-region even print these messages? > > There's the obvious case where write-region is called interactively. > I guess the behavior is inherited from this case. I presume, there is little chance to change this behaviour for noninteractive use? I understand, that these messages are important to many users in an *interactive* session, and that changing or removing them would be backwards-incompatible, but do these messages really matter in a *noninteractive* session? Is there really a need to inform about every single file being written to in Emacs Lisp scripts? I mean, there is no other programming language that behaves this way by default. > > > Stefan