From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.bugs Subject: bug#15576: 24.3.50; Some minor issues regarding the new TTY menus Date: Wed, 09 Oct 2013 20:52:37 -0400 Message-ID: References: <83zjqip7o4.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1381366400 9977 80.91.229.3 (10 Oct 2013 00:53:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 10 Oct 2013 00:53:20 +0000 (UTC) Cc: 15576@debbugs.gnu.org To: Dani Moncayo Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Oct 10 02:53:22 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1VU4VG-0005DK-3p for geb-bug-gnu-emacs@m.gmane.org; Thu, 10 Oct 2013 02:53:22 +0200 Original-Received: from localhost ([::1]:44470 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VU4VF-0002h2-8C for geb-bug-gnu-emacs@m.gmane.org; Wed, 09 Oct 2013 20:53:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43382) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VU4V5-0002gv-La for bug-gnu-emacs@gnu.org; Wed, 09 Oct 2013 20:53:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VU4Uw-0002Ba-3v for bug-gnu-emacs@gnu.org; Wed, 09 Oct 2013 20:53:11 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:58945) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VU4Uw-0002BV-0H for bug-gnu-emacs@gnu.org; Wed, 09 Oct 2013 20:53:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VU4Uv-0000T0-M7 for bug-gnu-emacs@gnu.org; Wed, 09 Oct 2013 20:53:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Monnier Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 10 Oct 2013 00:53:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15576 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 15576-submit@debbugs.gnu.org id=B15576.13813663611765 (code B ref 15576); Thu, 10 Oct 2013 00:53:01 +0000 Original-Received: (at 15576) by debbugs.gnu.org; 10 Oct 2013 00:52:41 +0000 Original-Received: from localhost ([127.0.0.1]:39003 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VU4Ua-0000SO-EZ for submit@debbugs.gnu.org; Wed, 09 Oct 2013 20:52:40 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:43148) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VU4UY-0000SH-Ra for 15576@debbugs.gnu.org; Wed, 09 Oct 2013 20:52:39 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EABK/CFFMCreE/2dsb2JhbABEuzWDWRdzgh4BAQQBViMFCwsOJhIUGA0kiB4GwS2RCgOSWpIggV6DEw X-IPAS-Result: Av8EABK/CFFMCreE/2dsb2JhbABEuzWDWRdzgh4BAQQBViMFCwsOJhIUGA0kiB4GwS2RCgOSWpIggV6DEw X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="35159402" Original-Received: from 76-10-183-132.dsl.teksavvy.com (HELO fmsmemgm.homelinux.net) ([76.10.183.132]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 09 Oct 2013 20:48:52 -0400 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id E68E9AE0C1; Wed, 9 Oct 2013 20:52:37 -0400 (EDT) In-Reply-To: (Dani Moncayo's message of "Wed, 9 Oct 2013 22:11:48 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.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-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:79130 Archived-At: > I think "Select Buffer" is wrong simply because it is different from > "Buffers". I mean, what is the point of showing one text (Buffers) > when the menu is not selected, and another text (Select Buffer) when > it is? I've not seen such a thing before anywhere, and I don't see > what sense it does make. You'd see it if you build Emacs with X11 but without GUI toolkit. This used to be the only case where the "keymap prompt" is used for the menus (it's also used for the title of the popup menus, tho). It's largely a historical accident, but here's the technical background: menus are represented in Emacs as keymaps which (as a first approximation) are alists mapping events to "menu-items". A menu-item is (again, to a first approximation) a pair of a chunk of text (to be displayed in the menu) and the corresponding binding (either a command or another keymap if it's a submenu). When you get a "submenu", the submenu is just the (sub)keymap, rather than the menu-item that holds this sub-keymap, so you don't know the name that was displayed for that submenu. So in order to display a "title", you need the keymap to carry a "name" (which is called the keymap-prompt). IOW for each submenu, you have 3 more or less equivalent/redundant "names": - the text to display in the parent menu (i.e. the only thing usually displayed). - the "prompt" (which is only displayed if you pass that submenu to directly popup-menu, or if you use the non-toolkit version of Emacs, or now in the tty-menu code). - the event associated with this submenu. It's usually a symbol rather than a string (because it's compared with `eq'; and it can also be an integer), but it's often just a symbol version of the "menu name". Those 3 can all be completely different, but normally/usually they're identical. > That's a pity. It would be nice to have those drop-down text menus > also on GUI sessions. Why? >> I tend to close this as not-a-bug. Any reasons not to? > See above, but you are the maintainer, so you decide. IIUC the issue is that fixing those things can represent a lot of work, whereas they fix only "cosmetic" issues, so it's difficult to justify the effort. Stefan