From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#36839: 26.1: unique frame names Date: Wed, 31 Jul 2019 11:13:40 +0200 Message-ID: References: <20190729161606.fyjwowadnuwe27zd@E15-2016.optimum.net> <83imrkkc6y.fsf@gnu.org> <20190729174933.jkov4mji5uovxlm6@E15-2016.optimum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="143909"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 36839@debbugs.gnu.org To: Boruch Baum , Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Jul 31 11:14:08 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hskgR-000bJ8-ML for geb-bug-gnu-emacs@m.gmane.org; Wed, 31 Jul 2019 11:14:07 +0200 Original-Received: from localhost ([::1]:39192 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hskgQ-0007Go-O2 for geb-bug-gnu-emacs@m.gmane.org; Wed, 31 Jul 2019 05:14:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58051) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hskgM-0007GW-U7 for bug-gnu-emacs@gnu.org; Wed, 31 Jul 2019 05:14:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hskgL-0005Oh-Vb for bug-gnu-emacs@gnu.org; Wed, 31 Jul 2019 05:14:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42724) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hskgL-0005O1-RH for bug-gnu-emacs@gnu.org; Wed, 31 Jul 2019 05:14:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hskgL-0003gM-Ln for bug-gnu-emacs@gnu.org; Wed, 31 Jul 2019 05:14:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 31 Jul 2019 09:14:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 36839 X-GNU-PR-Package: emacs Original-Received: via spool by 36839-submit@debbugs.gnu.org id=B36839.156456443214132 (code B ref 36839); Wed, 31 Jul 2019 09:14:01 +0000 Original-Received: (at 36839) by debbugs.gnu.org; 31 Jul 2019 09:13:52 +0000 Original-Received: from localhost ([127.0.0.1]:51545 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hskgB-0003fs-Oc for submit@debbugs.gnu.org; Wed, 31 Jul 2019 05:13:51 -0400 Original-Received: from mout.gmx.net ([212.227.15.15]:38225) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hskg9-0003ff-Q4 for 36839@debbugs.gnu.org; Wed, 31 Jul 2019 05:13:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1564564419; bh=dUtnVopQXELVHrJXmbim+a4v7UjSS/qVCiQubwY3uNA=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=Ft/6izVCMwiZjvlpdy/AXjUfm7UfGuSfZJqz+sdKkwQjjKs1CPvHGJw1jXtQBbcUa toxV8/tFMvQOiC5P6zuEp7iXE69wUsZAqLg7kAgqAdDOFUExSAhdRlFSJYk/CFzDLk M7W9JJfoRFCx7S5sSpZhTinmjSGgLpvYeByjkX50= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.101] ([213.162.73.223]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MGjfl-1i5gzC21oX-00DVzf; Wed, 31 Jul 2019 11:13:39 +0200 In-Reply-To: <20190729174933.jkov4mji5uovxlm6@E15-2016.optimum.net> Content-Language: de-DE X-Provags-ID: V03:K1:67tBCCJXUwkwlV+IqDvlqjQ/vaF39pgS3WuZ/Wfcfs6vhOa/A9s 9NR59baBn82zMgB1IUCwvbZAl22GEdUZMR6lA9/1uGtQNSBu3GQL+k4AyVRDyCs8Z8/ZzEL k76wXEw0Pi2sNTgEjUmODOTS/Yxe2AhMx7gCtvciYArpML0ylIOTejxH+tVlZSh9mCXgOSc Z6T2jVefes8Z1x51pQ+HA== X-UI-Out-Filterresults: notjunk:1;V03:K0:lc6YhXZ+A2w=:fALuoNwfJswfaxZeKz9yNu jiAJZ9+FRyfv3m4REGDJyD0c3QRiw7fwTPompeUxwwEsScqlNVhcjqcriNlClwGNPa+iQ7OW9 Z+Fcdjj6SyiTKy82b85IVw/VjBZZ7+iCEt+gAZazq2o8Bn2liqKzdVsCZqYJYr1/TPv9GUJFO y67kbYyGoT/+sPNG/79gXnoh89AOX8DmdUF4h2DtEjPubnOat6f9QG6H0os7kuS6Di7CCCFTg afETvhlzZgxFaor6K+YyiBlGK/ndyGdF5BOZseRx8sFLlI0o0hWj6TL0FE7bTuK9RrLpfrcg4 NbQEVDt22Lv6gEGm7Px94hd6rDh+MFG2juyHkPujAqdYl+ZiaIpXmwReLueQkv3cfm8xz2Jrf bBjYr1CzpBTdxm8PrMMwpM1NhnceF2u0VZO8OkI0Egmh6LkrobT9ApnmrAoSTr/MPkxa4YifL a0qNCrI3E+FkwGmUdAsdfSYJMuEZZ9bVnilB/8a9GWLba7tgT2cF/yFHeO+/R2EUU1s7R5wUh BIJIS3Hoca5+Nt3NxwDIJI2U0u6FTZ/IHljprl7Y/b6Nx+mLNTZRniKjhH1Tt9hmh22DU5c2C swvlguqQEi92zLV2zNNp4ClvpKwy/Uf778YnAxULbdBKbdsNQBxKyi6d5V1hrY2NeTb1y2YYJ EcHXSqoyYq3foQFGcC6nDT0fmrND7CCdKdpU4ywmiYxBUHWngXIH4PlGcBGUliDZS3asrbgVF YAi6YkMypIkP/0gka1AxEjmdLKPAQkauQYT+QyLOZ7V++1z/Vxchx7rXbLyT9ckS4gjZLy9+ X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:164152 Archived-At: > I'm using C-x 5 b (M-x select-frame-by-name) to switch between frames > and in my case, I would like the names to be more informative than just > Fnn. In a more general sense, if emacs is offering the NAME parameter, > it should assume the parameter will be used, and currently emacs isn't > handling its use well. I think the current behavior (using the name of the buffer of the selected window of each frame) works reasonably well as long as the same buffer doesn't appear in more than one selected window. It simply delegates your problem to the buffer naming mechanism. What you probably want is a mechanism that automatically assigns each frame an explicit, unique name at creation time. We could do that (optionally, because otherwise we would interfere with the default approach) but would have to invent a suitable naming scheme first. This is non-trivial because a naive numbering scheme where a user creates and subsequently deletes many frames might get out of hand soon. Such users need a mechanism for recycling the numbers of dead frames which might confuse other users who rarely create new frames. You could try putting a function that produces such names in your early init file, assign the values it produces to each newly created frame in a lambda you put on 'after-make-frame-functions' and tell us your experiences. martin