unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@gnu.org>
Cc: 10308@debbugs.gnu.org
Subject: bug#10308: 24.0.92; regression: *Help* ruined for toggling read-only
Date: Thu, 26 Apr 2012 06:51:07 -0700	[thread overview]
Message-ID: <F9ADBFA1BD934DFE91953D769D5A6465@us.oracle.com> (raw)
In-Reply-To: <87aa1znoaw.fsf@gnu.org>

> If you want to edit the buffer, switch to a major mode suitable for
> editing buffers.  Closing as wontfix.

There is no mode so suitable for editing *Help* as its own mode.

Changing the mode is not a reasonable workaround, as I reported:

>> Now, to be able to edit *Help* you need to change its mode,
>> instead of just hitting `C-x C-q'.  And if you are
>> iteratively fine-tuning doc for *Help*, then each time you
>> refresh it from developing code, you need to change the mode
>> again before you can edit it.

I get the impression that you have never used the capability of making *Help*
writable to develop a *Help* screen interactively & iteratively.  Otherwise,
this should be a no-brainer.

But even if you do not use this feature personally, surely you can understand
that others might.  And surely you can understand that what you have replaced it
with is useless to _everyone_.  Can you honestly make any argument in favor of
the new behavior when writable?  Is there any use case for it?  It is not even
consistent (e.g. DEL vs C-d).

It _appears_ that you did not read the bug report, or did not read it well.
Please (re-)read it.

When toggled to writable, you keep key bindings that make no sense in that
context.  You do not restore the normal keys, which do make sense.  There is now
no point in making the buffer writable.  You have taken away that functionality
for no reason - nothing useful or usable replaces it when the buffer is
writable.

And it is an incompatible change, but it is not even mentioned in NEWS.  How can
you in good conscience think there is no bug here?






      reply	other threads:[~2012-04-26 13:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16  7:35 bug#10308: 24.0.92; regression: *Help* ruined for toggling read-only Drew Adams
2012-04-26  3:51 ` Chong Yidong
2012-04-26 13:51   ` Drew Adams [this message]

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=F9ADBFA1BD934DFE91953D769D5A6465@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=10308@debbugs.gnu.org \
    --cc=cyd@gnu.org \
    /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).