From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John J Foerch Newsgroups: gmane.emacs.devel Subject: Re: request: make-frame-visible hook Date: Wed, 18 Feb 2009 20:27:15 -0500 Message-ID: <87vdr7i5cc.fsf@earthlink.net> References: <87zlgjis69.fsf@earthlink.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1235006648 20467 80.91.229.12 (19 Feb 2009 01:24:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Feb 2009 01:24:08 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 19 02:25:23 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LZxfH-0004Zk-M2 for ged-emacs-devel@m.gmane.org; Thu, 19 Feb 2009 02:25:23 +0100 Original-Received: from localhost ([127.0.0.1]:51317 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LZxdx-00014k-CK for ged-emacs-devel@m.gmane.org; Wed, 18 Feb 2009 20:24:01 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LZxdf-0000ns-QO for emacs-devel@gnu.org; Wed, 18 Feb 2009 20:23:43 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LZxde-0000lw-JB for emacs-devel@gnu.org; Wed, 18 Feb 2009 20:23:43 -0500 Original-Received: from [199.232.76.173] (port=55429 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LZxde-0000lj-CN for emacs-devel@gnu.org; Wed, 18 Feb 2009 20:23:42 -0500 Original-Received: from main.gmane.org ([80.91.229.2]:53928 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LZxdd-0004nV-VB for emacs-devel@gnu.org; Wed, 18 Feb 2009 20:23:42 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LZxdY-0006rS-8y for emacs-devel@gnu.org; Thu, 19 Feb 2009 01:23:36 +0000 Original-Received: from dialup-4.159.5.12.dial1.chicago1.level3.net ([4.159.5.12]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 Feb 2009 01:23:36 +0000 Original-Received: from jjfoerch by dialup-4.159.5.12.dial1.chicago1.level3.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 Feb 2009 01:23:36 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 38 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: dialup-4.159.5.12.dial1.chicago1.level3.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:UEhkEtU42OLrXTxzFBrWZKYSlmY= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:109204 Archived-At: Richard M Stallman writes: > I have used the emacs irc clients Circe and Erc, which both provide > modes to track activity in hidden irc buffers. "Hidden" may mean a > buffer that is not visible in any frame, or a buffer shown in a > non-visible frame. The irc channels with new activity are indicated in > the mode-line. Switching to a tracked buffer removes that buffer's > indicator from the mode-line. > > I don't think I would add an Emacs feature for the sake of this. > However, you might be able to get more or less the same result > by triggering off the arrival of output from a process or connection > and seeing which IRC buffers are currently displayed. What you describe is implemented in both of the irc clients I mentioned. They update the mode-line tracking indicator when new data arrives from the process, but this is not often enough, and it is the situation I would like to improve upon. A typical case for the new feature would be as follows: I have an emacs frame open on workspace 1, and my mode-line indicates that there is activity in an irc channel. I switch to workspace 2, where I have a frame showing the active irc channel. Without the ability to use the make-frame-visible event, the mode-line tracking indicator will continue to show that buffer, possibly for minutes until more data comes from the process. If I switch back to workspace 1, and the tracking indicator still has not been updated, I cannot then know when the next new data arrives from the process, because the indicator is now falsely on, though I have already read the buffer. I guess I am not sure what the point of having a make-frame-visible event is, if there can only be one handler on it. Thank you for your time. I hope you will reconsider. -- John Foerch