From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Masatake YAMATO Newsgroups: gmane.emacs.devel Subject: Re: |PATCH| describe-minor-mode and describe-minor-mode-from-indicator Date: Fri, 24 Jan 2003 02:40:30 +0900 (JST) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20030124.024030.39150801.jet@gyve.org> References: <20030121.010655.21600771.jet@gyve.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1043347701 28052 80.91.224.249 (23 Jan 2003 18:48:21 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 23 Jan 2003 18:48:21 +0000 (UTC) Cc: emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18bmNm-0007Dw-00 for ; Thu, 23 Jan 2003 19:47:22 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 18bmQA-0001wZ-00 for ; Thu, 23 Jan 2003 19:49:50 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18bmOF-0000ZQ-07 for emacs-devel@quimby.gnus.org; Thu, 23 Jan 2003 13:47:51 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18bmNs-0000MD-00 for emacs-devel@gnu.org; Thu, 23 Jan 2003 13:47:28 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18bmN8-00088s-00 for emacs-devel@gnu.org; Thu, 23 Jan 2003 13:46:45 -0500 Original-Received: from r-maa.spacetown.ne.jp ([210.130.136.40]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18bmN0-0007wA-00; Thu, 23 Jan 2003 13:46:34 -0500 Original-Received: from localhost (h219-110-074-122.catv01.itscom.jp [219.110.74.122]) by r-maa.spacetown.ne.jp (8.11.6) with ESMTP id h0NIkTY27276; Fri, 24 Jan 2003 03:46:29 +0900 (JST) Original-To: rms@gnu.org In-Reply-To: X-Mailer: Mew version 3.1.52 on Emacs 21.3 / Mule 5.0 (SAKAKI) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:11011 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:11011 I see you added a menu for major modes and also did what I suggested--to add a mouse command (which you put in the menu) to describe a minor mode or a major mode. What I was thinking of was to put the "describe" command on mouse-1 or mouse-2 rather than to put it in the menu. There is trade-off in two methods: just-one-click or choosing-from-menu. If you are familiar with Emacs, you will do not hesitate to click the mode line because you might know what happens next. You might be satisfied with quick operation. Further more, you might think GUI menu is a toy that make computer operation slow down. If you are new to Emacs, you must hesitate to click somewhere unknown/unfamiliar place on Emacs because you don't know what happens if you click. The mode line is one of the such place. The menu does not solve this issue perfectly. However, the menu's VISUAL FEEDBACK will much help for the emacs beginners. What I implemented is targeted on emacs beginners, so I used popup menu. Quick operation was not the my goal. How do you think? I used mouse-3, not mouse-1 and mouse-2 because Some gtk+/gnome applicaiton uses mouse-3 as context-menu. I expected Emacs beginners can use emacs's menu by analogy. Do you think we should bind all keys and mouse buttons with commands? (Yes, in my .emacs I've tried to bind super-* and hyper-* with many commands:-P) BTW, is there any policy about mouse button bindings; what kind of commands should be bound to mouse-1, what other kind of commands should be bound to mouse-2, and what another kind of commands should be bound to mouse-3? Binding any empty button to commands without policy will be cause of confusions. If it is already written in info, I have to read. In other hand, key binding policy for C-x prefix(global) and C-c prefix(mode specific) is understandable. Masatake YAMATO