unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
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: Mon, 22 Jul 2019 21:22:34 +0300	[thread overview]
Message-ID: <83y30qoro5.fsf@gnu.org> (raw)
In-Reply-To: <AxtmPA.j50qEU8YRvCW.aTBGDYWyncSTrjwaraBH@freemail.hu> (message from ndame on Mon, 22 Jul 2019 20:06:30 +0200 (CEST))

> From: ndame <emacsuser@freemail.hu>
> Date: Mon, 22 Jul 2019 20:06:30 +0200 (CEST)
> 
> > How about filing a feature-request bug report about this?
> 
> 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.

The usual reason is that what seems like a basic feature to you is not
necessarily that basic to others.  Which doesn't mean the feature
shouldn't exist, just that others may not assign the same importance
to it, and thus didn't implement it yet.

> Emacs uses single key bindings extensively elsewhere where the
> buffer is read only, so it's curious the addition of such quick
> keys did not come up before during the long history of emacs development.

As usual, this has a down-side: too many keys make them harder to
remember.



  reply	other threads:[~2019-07-22 18:22 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 [this message]
2019-07-22 18:40 ` Óscar Fuentes
2019-07-30 23:08 ` Emanuel Berg
  -- 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

  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=83y30qoro5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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.
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).