From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: [Bug] "You can't edit this part of the Custom buffer" Date: Thu, 27 Jul 2006 19:17:08 -0400 Message-ID: <87y7ue1vuz.fsf@stupidchicken.com> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1154042190 4593 80.91.229.2 (27 Jul 2006 23:16:30 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 27 Jul 2006 23:16:30 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 28 01:16:29 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 1G6F5g-0006Vj-5n for ged-emacs-devel@m.gmane.org; Fri, 28 Jul 2006 01:16:28 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G6F5f-0000wz-H4 for ged-emacs-devel@m.gmane.org; Thu, 27 Jul 2006 19:16:27 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G6F5T-0000wg-EC for emacs-devel@gnu.org; Thu, 27 Jul 2006 19:16:15 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G6F5S-0000wL-4h for emacs-devel@gnu.org; Thu, 27 Jul 2006 19:16:15 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G6F5R-0000wI-Uo for emacs-devel@gnu.org; Thu, 27 Jul 2006 19:16:13 -0400 Original-Received: from [18.19.1.138] (helo=cyd) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G6F7J-0003Nc-HL for emacs-devel@gnu.org; Thu, 27 Jul 2006 19:18:09 -0400 Original-Received: by cyd (Postfix, from userid 1000) id ECD124E2CA; Thu, 27 Jul 2006 19:17:08 -0400 (EDT) Original-To: "Drew Adams" In-Reply-To: (Drew Adams's message of "Thu, 27 Jul 2006 15:35:40 -0700") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:57701 Archived-At: > Why was this change made in the first place? It seems > pointless---Custom buffers are read-only, so self-insertion commands > do nothing anyway; we don't have to bind them to a 'custom-no-edit' > command that does nothing but raise an error. > > 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!)