From: Chong Yidong <cyd@stupidchicken.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 8147@debbugs.gnu.org
Subject: bug#8147: 24.0.50; Inserting *Help* buffer can lead to data loss
Date: Sun, 06 Mar 2011 15:28:43 -0500 [thread overview]
Message-ID: <87k4gct2mc.fsf@stupidchicken.com> (raw)
In-Reply-To: <87k4gcxkyp.fsf@escher.fritz.box> (Stephen Berman's message of "Sun, 06 Mar 2011 17:38:54 +0100")
Stephen Berman <stephen.berman@gmx.net> writes:
>> I just tested this with the doc string of help-buffer in *Help*. There
>> are two links in this doc string: clicking on `help-xref-following'
>> shows the error message "Current buffer is not in Help mode", which is
>> certainly better than overwriting the content of the buffer; but
>> clicking on `help-mode.el' finds that file and puts point on the
>> beginning of help-buffer's definition, i.e., still does what this kind
>> of link has always done. It is confusing to have this divergence in
>> behavior between the two kinds of links. Instead of signalling an
>> error, couldn't the help-xref-following buttons just show the help in
>> the *Help* buffer, as in the following patch?
The buffer from you pasted the button might not be *Help*; it could be
any other buffer in Help mode. So wouldn't it be inconsistent either
way?
next prev parent reply other threads:[~2011-03-06 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 16:02 bug#8147: 24.0.50; Inserting *Help* buffer can lead to data loss Stephen Berman
2011-03-02 17:07 ` Stefan Monnier
2011-03-05 21:10 ` Chong Yidong
2011-03-06 0:24 ` Stephen Berman
2011-03-06 16:38 ` Stephen Berman
2011-03-06 20:28 ` Chong Yidong [this message]
2011-03-06 23:41 ` Stephen Berman
2011-03-06 23:58 ` Stephen Berman
2011-03-07 16:20 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k4gct2mc.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=8147@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.