From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: Global bar to display global information Date: Tue, 16 Aug 2011 10:42:41 -0700 Message-ID: <22B4DB0E3E1C427EAB8A52C8C3B833A1@us.oracle.com> References: <87hb5he3dy.fsf@wanadoo.es> <87d3g5e19j.fsf@wanadoo.es> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1313516586 5754 80.91.229.12 (16 Aug 2011 17:43:06 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 16 Aug 2011 17:43:06 +0000 (UTC) To: "=?iso-8859-1?Q?'=D3scar_Fuentes'?=" , Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 16 19:43:00 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QtNfH-0002jz-3U for ged-emacs-devel@m.gmane.org; Tue, 16 Aug 2011 19:42:59 +0200 Original-Received: from localhost ([::1]:38443 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QtNfG-00013m-F3 for ged-emacs-devel@m.gmane.org; Tue, 16 Aug 2011 13:42:58 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:46714) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QtNfD-00012x-0e for emacs-devel@gnu.org; Tue, 16 Aug 2011 13:42:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QtNfB-0000mn-7b for emacs-devel@gnu.org; Tue, 16 Aug 2011 13:42:54 -0400 Original-Received: from rcsinet15.oracle.com ([148.87.113.117]:56504) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QtNfB-0000mU-2V for emacs-devel@gnu.org; Tue, 16 Aug 2011 13:42:53 -0400 Original-Received: from rtcsinet21.oracle.com (rtcsinet21.oracle.com [66.248.204.29]) by rcsinet15.oracle.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id p7GHgnwJ025978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 16 Aug 2011 17:42:51 GMT Original-Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by rtcsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id p7GHgmxJ003639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Aug 2011 17:42:49 GMT Original-Received: from abhmt101.oracle.com (abhmt101.oracle.com [141.146.116.53]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p7GHggWM009495; Tue, 16 Aug 2011 12:42:42 -0500 Original-Received: from dradamslap1 (/10.159.52.231) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 16 Aug 2011 10:42:42 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <87d3g5e19j.fsf@wanadoo.es> Thread-Index: AcxcNqYBt8gFHxAUTEiYOK6dbjTjhgAAHwAg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 X-Source-IP: rtcsinet21.oracle.com [66.248.204.29] X-CT-RefId: str=0001.0A090205.4E4AAC1B.008D,ss=1,re=0.000,fgs=0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 1) X-Received-From: 148.87.113.117 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:143321 Archived-At: > If [reusing the minibuffer area] is not possible or convenient, > a dedicated line on each frame looks like the next choice. If it is on each frame then the feature doesn't really factor out the global info. Since you use only one frame, "on each frame" just hides the general-case duplication from you. > (If the global info line is displayed on just one frame, what happens > when the user creates a new frame on a remote display?) Dunno. (But why would you want this info on *each* remote frame?) So make it one frame per display (remotes + local), instead of just one frame overall. Or I suppose users could configure some option to specify just which frames to use... (Hello, Martin ;-)) Essentially, what's requested is some stable place to post (and leave posted) a bit of general info - info that is not specific to any buffer or window or frame... What you feel about windows should also hold for frames: get rid of the duplication. That you use only one frame does not mean that that need goes away for others who might like the feature. It makes most sense not to duplicate that info anywhere, with the possible exception I guess that it could be available (once) on each display (e.g. each remote display, plus local). That means not on every frame and not on every window. It means either giving it its own, dedicated frame (frames, if we include remote) or posting it in some existing frame (e.g. standalone minibuffer frame). And the info need not be limited to a single line. Especially if it is in a dedicated frame, it could use any number of lines. This could be done easily now, just by using a dedicated frame. Instead of posting your global info to the mode line, just display it in a buffer that uses a special frame (which is dedicated). Yes, that's different from (somehow) gathering up some common, global stuff from existing mode lines and displaying it elsewhere. But how to identify such factorable info in existing mode lines? Anyway, it sounds like the main case (OP) was user code that displays such stuff in the mode line. If that hurts then don't do it - instead, put it in a special-display buffer in its own frame. For my part, I still think it could be useful to (be able to) add the info to a standalone minibuffer frame. One difference from having a separate frame for it is that that would save the real estate of an extra frame title and border.