From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mark H Weaver Newsgroups: gmane.lisp.guile.devel Subject: Re: Discussion for %display-auto-compilation-messages (and --no-auto-compilation-messages option) Date: Tue, 25 Mar 2014 22:34:00 -0400 Message-ID: <8761n1k7s7.fsf@yeeloong.lan> References: <53125A46.3010407@gmail.com> <87a9d8tib7.fsf@gnu.org> <87r45qov0b.fsf@pobox.com> <87vbv23rhy.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1395801303 29861 80.91.229.3 (26 Mar 2014 02:35:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 26 Mar 2014 02:35:03 +0000 (UTC) Cc: Andy Wingo , guile-devel@gnu.org To: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Wed Mar 26 03:35:12 2014 Return-path: Envelope-to: guile-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 1WSdgL-00049L-N2 for guile-devel@m.gmane.org; Wed, 26 Mar 2014 03:35:09 +0100 Original-Received: from localhost ([::1]:45261 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSdgK-0007cT-Qn for guile-devel@m.gmane.org; Tue, 25 Mar 2014 22:35:08 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58370) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSdg6-0007Yu-Ia for guile-devel@gnu.org; Tue, 25 Mar 2014 22:34:59 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WSdg1-000083-3K for guile-devel@gnu.org; Tue, 25 Mar 2014 22:34:54 -0400 Original-Received: from world.peace.net ([96.39.62.75]:34097) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSdg0-000076-Ux; Tue, 25 Mar 2014 22:34:49 -0400 Original-Received: from 209-6-91-212.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([209.6.91.212] helo=yeeloong.lan) by world.peace.net with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1WSdft-0003Vp-4N; Tue, 25 Mar 2014 22:34:41 -0400 In-Reply-To: <87vbv23rhy.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 25 Mar 2014 22:20:09 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 96.39.62.75 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:17019 Archived-At: ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Andy Wingo skribis: > >> On Sun 02 Mar 2014 22:13, ludo@gnu.org (Ludovic Court=C3=A8s) writes: >> >>> FWIW, I think the approach should rather be to have a special port (a >>> fluid) for such things, say, =E2=80=98current-notification-port=E2=80= =99. We=E2=80=99d simply >>> replace scm_current_error_port by scm_current_notication_port above. >> >> Isn't that the same as current-warning-port? I thought this was one of >> the use cases for current-warning-port :) > > Yeah it=E2=80=99s very similar, but we could want to differentiate between > actual warnings and mere notifications. Dunno if it=E2=80=99s important. One issue worth thinking about is that there are cases where code has to parameterize all of these port parameters. For example, I recently discovered that REPL Servers weren't redirecting the warning port to the socket, so warnings about expressions typed on a REPL server were being sent to the main program's stderr. I fixed this in 5e74217c7cf07ad474cdce1a01e049492e7ef1b7, but if we add another port parameter I'll have to fix that in at least two places now: server.scm and coop-server.scm. I wonder if external code needs to sometimes do this as well. How will they cope with a periodically-expanding set of port parameters, while retaining compatible with older versions of guile that lack some of them? Should we add a 'parameterize-all-stdout-like-ports' macro? Mark