From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.devel Subject: Re: cus-misc: customize autoloads, environment variables (and key bindings) Date: Wed, 21 Apr 2004 22:13:34 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1082579407 13730 80.91.224.253 (21 Apr 2004 20:30:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 21 Apr 2004 20:30:07 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Apr 21 22:29:54 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BGOLy-0000GB-00 for ; Wed, 21 Apr 2004 22:29:54 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BGOLy-0001la-00 for ; Wed, 21 Apr 2004 22:29:54 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BGOLs-0006S6-7O for emacs-devel@quimby.gnus.org; Wed, 21 Apr 2004 16:29:48 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BGOLW-0006MV-Lo for emacs-devel@gnu.org; Wed, 21 Apr 2004 16:29:26 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BGOFs-0004MZ-EU for emacs-devel@gnu.org; Wed, 21 Apr 2004 16:24:11 -0400 Original-Received: from [217.13.230.178] (helo=yxa.extundo.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.30) id 1BGO6H-00026m-CC; Wed, 21 Apr 2004 16:13:41 -0400 Original-Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.12.11/8.12.11) with ESMTP id i3LKDZTI012908 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 21 Apr 2004 22:13:35 +0200 Original-To: rms@gnu.org X-Hashcash: 0:040421:rms@gnu.org:73f323fc78dd1f6b X-Hashcash: 0:040421:emacs-devel@gnu.org:defb4cd356e6f94b In-Reply-To: (Richard Stallman's message of "Wed, 21 Apr 2004 14:58:31 -0400") User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:22005 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:22005 Richard Stallman writes: > I think the `repeat' customization widget is rather inconvenient to > use. > > I think that it is a mistake for [Ins] and [Del] to look similar. > They do entirely different kinds of things. [Del] applies to an > existing entry, but [Ins] does not. Having two similar-looking > buttons for these two disparate operations can't help being confusing. > > Also, there is no way to reorder existing entries except to delete > some and reinsert them from zero. > > This suggests the idea that the interface should provide a way to > (1) delete any entry > (2) move any entry to a new position > (3) insert a new entry at the front > > [Del] and [Move] would both apply to an existing entry, so it would > make sense to have these two buttons side by side. Instead of [Ins], > which is cryptic, we could have [Add new entry]. There would only > be one such button, at the start of the list, so a long name is ok. > > With this change, perhaps these methods of customizing key bindings > and env vars would be convenient enough to use. Perhaps the "Move" idea can be refined by providing two buttons, one "Move Up" and one "Move down" (possibly using some arrow glyph). I believe this is commonly used in other GUIs, so users should be familiar with it. The alternative, of having only one "Move" button, implies clicking on that should question the user somehow, on where she wants to move the entry. This might get complicated. But otherwise I think the suggestions are good. Alas, I don't have time, right now, to learn how custom widgets work to implement this.