From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mathias Dahl Newsgroups: gmane.emacs.devel Subject: Re: foreground menu bug Date: Mon, 27 Jun 2005 10:22:15 +0200 Message-ID: References: <20050615.071604.11389732.wl@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1119862707 19149 80.91.229.2 (27 Jun 2005 08:58:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 27 Jun 2005 08:58:27 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 27 10:58:25 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DmpRA-0004JO-9H for ged-emacs-devel@m.gmane.org; Mon, 27 Jun 2005 10:57:52 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DmpYm-0004r9-1u for ged-emacs-devel@m.gmane.org; Mon, 27 Jun 2005 05:05:44 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DmpLx-0007Dw-61 for emacs-devel@gnu.org; Mon, 27 Jun 2005 04:52:34 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DmpLt-0007Bw-Ew for emacs-devel@gnu.org; Mon, 27 Jun 2005 04:52:26 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dmp7V-00060n-Ok for emacs-devel@gnu.org; Mon, 27 Jun 2005 04:37:36 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1DmoxZ-0005qG-8J for emacs-devel@gnu.org; Mon, 27 Jun 2005 04:27:17 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DmomG-0004Nz-Bb for emacs-devel@gnu.org; Mon, 27 Jun 2005 10:15:36 +0200 Original-Received: from user.ifsab.se ([193.41.170.225]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 Jun 2005 10:15:36 +0200 Original-Received: from brakjoller by user.ifsab.se with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 Jun 2005 10:15:36 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 22 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: user.ifsab.se User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (windows-nt) Cancel-Lock: sha1:MtXJdjO9e3lkNO/JzLlQymZwnBo= 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:39635 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:39635 "Richard M. Stallman" writes: > Or, it could just warn the user that the highlighting will not be > visible since font lock is enabled? > > It would be possible, but why be so complicated? > This change seems to do the right job. Assuming the user notices that we disabled the menu item, your fix might work. What about users who use M-x apropos or similar to find commands and then used enter the commands with M-x, how would they know that this comment is currently "disabled", or not meant to be used? Also, what does a disabled menu item tell the user? He might not understand that it is because font lock is enabled. He might wonder if he is doing something wrong seeing that menu item disabled. I think this is a bad idea which just avoids solving the real problem. If we disable the menu item, which is one way for the user to execute the command, we should also disabled the other ways to execute that command. Or make the command warn the user in some way.