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: Simple Tasks, new TODO category Date: Wed, 23 Jan 2008 15:59:01 -0800 Message-ID: References: <4797CB65.7040401@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1201132767 11670 80.91.229.12 (23 Jan 2008 23:59:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 23 Jan 2008 23:59:27 +0000 (UTC) Cc: Dan Nicolaescu , emacs-devel@gnu.org To: "Lennart Borgman \(gmail\)" , "Jason Rumney" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 24 00:59:46 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 1JHpVM-0005Ip-MF for ged-emacs-devel@m.gmane.org; Thu, 24 Jan 2008 00:59:40 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JHpUw-0007XK-Ni for ged-emacs-devel@m.gmane.org; Wed, 23 Jan 2008 18:59:14 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JHpUs-0007V4-ER for emacs-devel@gnu.org; Wed, 23 Jan 2008 18:59:10 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JHpUq-0007T9-RI for emacs-devel@gnu.org; Wed, 23 Jan 2008 18:59:10 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JHpUq-0007Sz-Np for emacs-devel@gnu.org; Wed, 23 Jan 2008 18:59:08 -0500 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 1JHpUm-00032d-KJ; Wed, 23 Jan 2008 18:59:04 -0500 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 m0NNwrID010919; Wed, 23 Jan 2008 16:58:53 -0700 Original-Received: from acsmt351.oracle.com (acsmt351.oracle.com [141.146.40.151]) by agmgw2.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id m0N0JdvK010030; Wed, 23 Jan 2008 16:58:53 -0700 Original-Received: from dhcp-amer-csvpn-gw1-141-144-67-90.vpn.oracle.com by acsmt351.oracle.com with ESMTP id 3533387851201132731; Wed, 23 Jan 2008 15:58:51 -0800 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <4797CB65.7040401@gmail.com> Importance: Normal 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-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:87408 Archived-At: > However the most easy way to do that is probably to add a character to > the menu title string that could not possibly be part of the title. That > way we could easily support w32 and, eh what window manager (is that > what handles menus?) used _ to mark the accelerator? (Jan D, I think it > was you that told about this when I asked before. GNOME?) > > Is there any drawback with such a simple design? Could we for example > use char number 1? It should be very easy to implement for w32 and the > other case above (where char 1 is just replaced with & and the other > case where it is replaced with _). I haven't followed this. But I would be against having any (printable) character in a menu-item name be interpreted specially and not just treated as part of the name. It is not the case that some (printable) character "could not possibly be part of the title" - whatever (printable) character you choose, someone will want to use it in a menu item. `_' can certainly be useful in a name. I don't know if that is what you meant, but if it is, please find some other mechanism, or at least allow for escaping the instruction character. An alternative might be to use an unprintable character.