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: [Bug] "You can't edit this part of the Custom buffer" Date: Thu, 27 Jul 2006 20:03:03 -0700 Message-ID: References: <87y7ue1vuz.fsf@stupidchicken.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1154055871 636 80.91.229.2 (28 Jul 2006 03:04:31 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 28 Jul 2006 03:04:31 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 28 05:04:30 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G6IeL-0007Ay-A7 for ged-emacs-devel@m.gmane.org; Fri, 28 Jul 2006 05:04:29 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G6IeK-00080q-Ej for ged-emacs-devel@m.gmane.org; Thu, 27 Jul 2006 23:04:28 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G6Ie9-00080U-4p for emacs-devel@gnu.org; Thu, 27 Jul 2006 23:04:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G6Ie7-00080A-Mg for emacs-devel@gnu.org; Thu, 27 Jul 2006 23:04:16 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G6Ie7-000807-EB for emacs-devel@gnu.org; Thu, 27 Jul 2006 23:04:15 -0400 Original-Received: from [141.146.126.228] (helo=agminet01.oracle.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1G6Ig0-00029D-UH for emacs-devel@gnu.org; Thu, 27 Jul 2006 23:06:13 -0400 Original-Received: from rcsmt250.oracle.com (rcsmt250.oracle.com [148.87.90.195]) by agminet01.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k6R4Gxhv012708 for ; Thu, 27 Jul 2006 22:04:13 -0500 Original-Received: from dhcp-amer-csvpn-gw2-141-144-72-40.vpn.oracle.com by rcsmt250.oracle.com with ESMTP id 1665283691154055783; Thu, 27 Jul 2006 21:03:03 -0600 Original-To: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <87y7ue1vuz.fsf@stupidchicken.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 X-Whitelist: TRUE 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:57711 Archived-At: > I'm not responsible for the fix, but I reported the bug that was > fixed: See the thread "Customize buffer modification: indicator, > feedback, undo" in emacs-pretest, of June 10-11, 2006. From your bug report: 2. Trying to type in the header text has no effect. There should be a message indicating that that area of text is read-only. Otherwise, with no feedback, the user doesn't understand what's happening and why. I think this is an unreasonable quibble. With the old behavior, when you try to insert something in a Customize buffer, you get an error: "Text is read-only: Attempt to change text outside editable field" Now, you get the error: "You can't edit this part of the Custom buffer" The difference is negligible. No user is going to get confused about why they can't edit the Customize buffer---it's obvious, from the appearance of the buffer, which contains buttons and hyperlinks, that it's not meant to be edited. (In a similar vein, we don't worry that users will type "s" in an Info buffer and be shocked that it runs Info-search instead of inserting text!) No. Please read my bug report again. I said "has no effect". And I said "with no feedback". And that was the behavior at the time: nothing, nada, zip - no feedback to the user. You hit a key, and you see no effect and no message. I just retested, to be sure, BTW. I have no problem with either message that you quote. The problem was that there was no message at all. Every user action deserves some perceptible change or feedback.