From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: RE: should frame names be unique? Date: Fri, 21 Mar 2008 13:28:28 -0700 Message-ID: <007001c88b92$1f99ac30$0600a8c0@us.oracle.com> References: <003d01c88b69$e16c0980$0600a8c0@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1206131357 9901 80.91.229.12 (21 Mar 2008 20:29:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 21 Mar 2008 20:29:17 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, 'Damon Permezel' , 'Emacs-Devel' To: "'Stefan Monnier'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 21 21:29:47 2008 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 1Jcnrz-0000b2-RD for ged-emacs-devel@m.gmane.org; Fri, 21 Mar 2008 21:29:44 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JcnrP-0003f9-B6 for ged-emacs-devel@m.gmane.org; Fri, 21 Mar 2008 16:29:07 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jcnr3-0003X4-4o for emacs-devel@gnu.org; Fri, 21 Mar 2008 16:28:45 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jcnr2-0003WE-8J for emacs-devel@gnu.org; Fri, 21 Mar 2008 16:28:44 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jcnr1-0003W2-Rs for emacs-devel@gnu.org; Fri, 21 Mar 2008 16:28:43 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jcnr1-00070X-H9 for emacs-devel@gnu.org; Fri, 21 Mar 2008 16:28:43 -0400 Original-Received: from mx10.gnu.org ([199.232.76.166]) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1Jcnr1-0007KJ-7N for emacs-pretest-bug@gnu.org; Fri, 21 Mar 2008 16:28:43 -0400 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Jcnqx-0006zR-Vj for emacs-pretest-bug@gnu.org; Fri, 21 Mar 2008 16:28:43 -0400 Original-Received: from rgminet01.oracle.com ([148.87.113.118]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jcnqx-0006z9-Hr; Fri, 21 Mar 2008 16:28:39 -0400 Original-Received: from agmgw2.us.oracle.com (agmgw2.us.oracle.com [152.68.180.213]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id m2LKSVfC029159; Fri, 21 Mar 2008 14:28:32 -0600 Original-Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by agmgw2.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id m2K24QBw019077; Fri, 21 Mar 2008 14:28:31 -0600 Original-Received: from inet-141-146-46-1.oracle.com by acsmt350.oracle.com with ESMTP id 3621886101206131303; Fri, 21 Mar 2008 13:28:23 -0700 Original-Received: from dradamslap1 (/141.144.80.154) by bhmail.oracle.com (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 21 Mar 2008 13:28:23 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Thread-Index: AciLgNEVDrWl9+u+QciUBGjbJVCvrwAAtdWQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 X-detected-kernel: by monty-python.gnu.org: 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:93139 gmane.emacs.pretest.bugs:21638 Archived-At: > > It is not the best design to have multiple frames with the > > same name. When you choose a frame by its name via the > > minibuffer or a menu, it's possible to see duplicate names > > that represent different frames - there is then no way to > > know which name corresponds to which frame. > > Try > > (setq frame-title-format > '(multiple-frames ("F" > (:eval (number-to-string > (length (memq (selected-frame) > (frame-list))))) > " %b") > ("" invocation-name "@" system-name))) This is about commands that interact with user frames. It's not appropriate to ask users to name their frames in some particular way. But perhaps I misunderstand you. > I'm not opposed to making frame names unique, but first, I'd like to > hear about the use-cases where it matters. Think of the Frames menu. If you have multiple frames showing the same buffer, then you will have multiple identical entries in the Frames menu. No way to know which is which, which makes them pretty useless. > I.e. what uses of frame-names are we talking about > (select-frame-by-name? The Frames menu?)? Yes, both. Though select-frame-by-name apparently removes duplicates, so AFAICT it doesn't even let you select some of the frames (a bug?). (The example that brought this up was an Icicles multi-command version of select-frame-by-name.) > What is the difference between those frames showing the same buffer > (is it just to display two different parts of a buffer, if so do the > various frames play different roles? Are they on different screens? > Can you see their names in the title bar? ...) I can't answer any of those questions. Perhaps Damon can. He is the one who reported the problem using multiple frames with the same name.