unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: [Bug] "You can't edit this part of the Custom buffer"
Date: Thu, 27 Jul 2006 20:03:03 -0700	[thread overview]
Message-ID: <MEEKKIABFKKDFJMPIOEBEEMEDDAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87y7ue1vuz.fsf@stupidchicken.com>

    > 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.

  reply	other threads:[~2006-07-28  3:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 13:12 [Bug] "You can't edit this part of the Custom buffer" David Abrahams
2006-07-27 13:38 ` Johan Bockgård
2006-07-27 14:06   ` David Abrahams
2006-07-27 15:21   ` Drew Adams
2006-07-27 22:22     ` Chong Yidong
2006-07-27 22:35       ` Drew Adams
2006-07-27 23:17         ` Chong Yidong
2006-07-28  3:03           ` Drew Adams [this message]
2006-07-28 13:32             ` Chong Yidong
2006-07-28 13:54               ` Drew Adams
2006-07-28 18:18                 ` Chong Yidong
2006-07-28 18:29                   ` Drew Adams
2006-07-28 19:01                     ` Chong Yidong
2006-07-28 13:34           ` Richard Stallman
2006-07-28 18:14             ` Chong Yidong
2006-07-29  2:59               ` Richard Stallman
2006-07-27 21:49 ` Richard Stallman
2006-07-27 22:35   ` David Abrahams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MEEKKIABFKKDFJMPIOEBEEMEDDAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).