From: Juri Linkov <juri@jurta.org>
To: martin rudalics <rudalics@gmx.at>
Cc: ian@iankelling.org, 17210@debbugs.gnu.org
Subject: bug#17210: 24.3.50; help mode [back] link to a C-h b keybind listing fails with message "Current buffer is not in Help mode"
Date: Tue, 08 Apr 2014 11:32:27 +0300 [thread overview]
Message-ID: <87d2gskyp2.fsf@mail.jurta.org> (raw)
In-Reply-To: <5343A1BC.6030307@gmx.at> (martin rudalics's message of "Tue, 08 Apr 2014 09:14:04 +0200")
> It fixes the OP's problem so please check it in. But when hitting the
> back button you don't get the previous contents. I suppose we have to
> add the original buffer to the `help-args' of that button, but I leave
> that to Juri.
In the recent discussion at http://thread.gmane.org/gmane.emacs.devel/168353
the idea was to store the previous content in hidden Help buffers
(buffer names starting with a space).
> In any case, the behavior is broken since Emacs 24.3 at least
> (but I suppose it's broken ever since).
For `C-h b' it was broken by design because after killing the initial buffer:
1. C-h b
2. click function name link
3. kill *scratch*
4. click back
clicking on [back] fails with the error "Selecting deleted buffer".
next prev parent reply other threads:[~2014-04-08 8:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 23:47 bug#17210: 24.3.50; help mode [back] link to a C-h b keybind listing fails with message "Current buffer is not in Help mode" Ian Kelling
2014-04-07 7:48 ` martin rudalics
2014-04-07 15:54 ` Eli Zaretskii
2014-04-07 18:17 ` Stefan Monnier
2014-04-08 7:14 ` martin rudalics
2014-04-08 8:32 ` Juri Linkov [this message]
2014-04-08 9:18 ` martin rudalics
2014-04-08 15:27 ` Eli Zaretskii
2014-04-08 16:34 ` martin rudalics
2014-04-08 16:42 ` Eli Zaretskii
2014-04-08 17:01 ` martin rudalics
2014-04-08 17:08 ` martin rudalics
2014-04-08 17:16 ` Andreas Schwab
2014-04-08 7:13 ` martin rudalics
2014-04-08 15:26 ` Eli Zaretskii
2014-04-08 19:49 ` 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
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=87d2gskyp2.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=17210@debbugs.gnu.org \
--cc=ian@iankelling.org \
--cc=rudalics@gmx.at \
/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).