all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 55019@debbugs.gnu.org
Cc: laszlomail@protonmail.com
Subject: bug#55019: Pressing RET on header line of help buffer describing a lisp entity should go to the source
Date: Tue, 19 Apr 2022 13:33:34 +0200	[thread overview]
Message-ID: <m1y2015mup.fsf@yahoo.es> (raw)
In-Reply-To: <xvmlEGawuLnplpgzVQd0rm0-n7uiR4SfAkiio0Avu73E5-QBwpxY8Yox93ProulAVbRER1Rcs_nxJkywWtA_K8CyNSyJbicNxGzgKMGeLF8=@protonmail.com> (emacsq via's message of "Tue, 19 Apr 2022 09:21:13 +0000")

emacsq via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:

> E.g. take describe-function: diff
>
> The first line:
>
> diff is an autoloaded interactive compiled Lisp function in ‘diff.el’.
>
> The line describes what this entity is and where it is defined. If I want to look it up, then I have to press TAB to go to the link and then RET.
>
> Since RET does not do anything useful on help text anyway, it's more
> convenient if RET goes to the source when pressed anywhere on the
> opening text describing the entity, without having to press TAB first.

Since Emacs 28.1, you can press "s" in the *Help* buffer to go directly
to the source.





      parent reply	other threads:[~2022-04-19 11:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19  9:21 bug#55019: Pressing RET on header line of help buffer describing a lisp entity should go to the source emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-19 11:30 ` Lars Ingebrigtsen
2022-04-19 11:33 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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=m1y2015mup.fsf@yahoo.es \
    --to=bug-gnu-emacs@gnu.org \
    --cc=55019@debbugs.gnu.org \
    --cc=laszlomail@protonmail.com \
    --cc=mardani29@yahoo.es \
    /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.