From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Silencing noise Date: Mon, 13 Apr 2015 18:32:36 +0300 Message-ID: <83mw2ccacr.fsf@gnu.org> References: <87oams5uwn.fsf@gmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1428939166 31365 80.91.229.3 (13 Apr 2015 15:32:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 13 Apr 2015 15:32:46 +0000 (UTC) Cc: flexibeast@gmail.com, emacs-devel@gnu.org To: raman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 13 17:32:39 2015 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 1YhgLl-0003h1-Iy for ged-emacs-devel@m.gmane.org; Mon, 13 Apr 2015 17:32:37 +0200 Original-Received: from localhost ([::1]:52365 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhgLl-00075M-16 for ged-emacs-devel@m.gmane.org; Mon, 13 Apr 2015 11:32:37 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41324) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhgLi-00075E-At for emacs-devel@gnu.org; Mon, 13 Apr 2015 11:32:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YhgLf-0005S0-5K for emacs-devel@gnu.org; Mon, 13 Apr 2015 11:32:34 -0400 Original-Received: from mtaout21.012.net.il ([80.179.55.169]:44561) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhgLe-0005Qy-Tr for emacs-devel@gnu.org; Mon, 13 Apr 2015 11:32:31 -0400 Original-Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0NMR00H004E2FS00@a-mtaout21.012.net.il> for emacs-devel@gnu.org; Mon, 13 Apr 2015 18:32:27 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NMR00HG44I3C1A0@a-mtaout21.012.net.il>; Mon, 13 Apr 2015 18:32:27 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.169 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:185372 Archived-At: > From: raman > Date: Mon, 13 Apr 2015 08:16:39 -0700 > Cc: emacs-devel@gnu.org > > Long-term it would be nice if message could be aware of the frame/thread > from where it was launched --- thinking forward to > concutrrent/multi-threaded emacs, it would be ideal if messages > displayed from a thread running in a frame was limited to that frame. You are IMO making too many hidden assumptions about those, as yet non-existing, future features, for example that there can be such a thing as a "thread running on a frame". To me, the most important objection to limiting a message to some frame is that by the time the message is displayed that frame might no longer be current/visible, and might not even exist. > Food for thought: Should we in that world have a single *Messages* > buffer where all messages land up -- or a per-frame *Messages* buffer > with an additional Global-Messages buffer that shows up everywhere -- > that message queue could then be sued to display truly urgent alerts > etc. I'd like to see the concurrency branch revived and actively developed to maturity, before I develop appetite for that kind of food.