From: Eli Zaretskii <eliz@gnu.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 19:42:40 +0300 [thread overview]
Message-ID: <83txa36adb.fsf@gnu.org> (raw)
In-Reply-To: <5344251E.7080501@gmx.at>
> Date: Tue, 08 Apr 2014 18:34:38 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: monnier@IRO.UMontreal.CA, ian@iankelling.org, 17210@debbugs.gnu.org,
> juri@jurta.org
>
> > If "back" doesn't get you back, then it isn't really a solution, is
> > it?
>
> My first conclusion was wrong. "back" gets me the right buffer but it
> gives me different contents.
That is a different problem, and AFAIK it is not new: try the same in
Emacs from before your pixelwise resize changes, and I think you will
see the same behavior.
> and *Help* has 1637 lines. Confusing. I think I'll have to debug
> `describe-buffer-bindings' to find out what happens.
I think it simply describes bindings in another buffer (*Help* instead
of *scratch*).
next prev parent reply other threads:[~2014-04-08 16:42 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
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 [this message]
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=83txa36adb.fsf@gnu.org \
--to=eliz@gnu.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).