From: Emanuel Berg <moasenwood@zoho.eu>
To: help-gnu-emacs@gnu.org
Subject: Re: Why there is no key in the *Help* buffer to bring up the relevant info page?
Date: Wed, 31 Jul 2019 01:08:16 +0200 [thread overview]
Message-ID: <86v9vj3yu7.fsf@zoho.eu> (raw)
In-Reply-To: AxtmPA.j50qEU8YRvCW.aTBGDYWyncSTrjwaraBH@freemail.hu
ndame wrote:
> I may do that, I just asked here, because it
> seemed strange that the help buffer missed
> such a basic feature, though I think many
> elisp developers like me wanted to navigate
> to info from help in the past.
Good idea. The info crosslink, I mean.
But by all means, it is also a good idea to
report it as a bug. `report-emacs-bug' perhaps
doesn't sound like the place to file
suggestions, but it is, nonetheless. (Yeah...
actually it _is_ a bit confusing
and intimidating!)
But: You can post your suggestion here as well!
And perhaps it is a good idea to do so since
who knows, perhaps someone here knows of
a package to solve the issue, or a reason why
it isn't already there, or just someone telling
you ... you should report it as a bug :)
> And also, I very often go to the source code
> of a function from Help to peruse it, so the
> s key (also unbound) could go to the source
> code quickly.
I just hammer TAB do go between buttons and
then hit RET to get to the code. I don't think
I'd gain so much speed from the s key doing the
same thing, but strictly speaking, I should at
least gain some, and it makes sense as well -
so yes, I think this is a good idea as well :)
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2019-07-30 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 18:06 Why there is no key in the *Help* buffer to bring up the relevant info page? ndame
2019-07-22 18:22 ` Eli Zaretskii
2019-07-22 18:40 ` Óscar Fuentes
2019-07-30 23:08 ` Emanuel Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-22 18:56 ndame
2019-07-22 20:41 ` Drew Adams
2019-07-22 15:37 ndame
2019-07-22 17:34 ` Eli Zaretskii
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=86v9vj3yu7.fsf@zoho.eu \
--to=moasenwood@zoho.eu \
--cc=help-gnu-emacs@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 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.