unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: [SOLVED with eev] Re: How to quicker jump to function definition than C-h k ?
Date: Fri, 16 Dec 2022 16:39:12 +0300	[thread overview]
Message-ID: <Y5x1AG7H8AnD1eK7@protected.localdomain> (raw)
In-Reply-To: <CADs++6gAUQuNTvvSgAx0nz3dW5qP3gbXzpjW45THL_bBVaA9bw@mail.gmail.com>

* Eduardo Ochs <eduardoochs@gmail.com> [2022-12-16 11:14]:
> ;; Try: (eek "M-h M-k  <right>")
> ;;      (eek "M-h M-k  <right>   12*<down>")
> ;;      (eek "M-h M-k  <right>   12*<down> M-e")
> ;;      (eek "M-h M-k  M-h M-k  ;; find-ekey-links")
> ;;      (find-efunction 'find-ekey-links)
> ;;      (find-efunction 'ee-find-eboundkey-links)
> ;;      (find-definition-for-key (kbd "<right>"))
> 
 (defun find-definition-for-key (key &rest pos-spec-list)
 "Based on `find-ekey-links' (`M-h M-k') and `find-efunction'."
   (interactive "kFunction definition for Key: ")
   (find-efunction (key-binding key)))

 (defalias 'fdk 'find-definition-for-key)

Much thanks.

(global-set-key (kbd "C-c k") 'find-definition-for-key)

Now I can jump straight to function definition.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  reply	other threads:[~2022-12-16 13:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  6:19 How to quicker jump to function definition than C-h k ? Jean Louis
2022-12-16  8:01 ` Marcin Borkowski
2022-12-16  8:13 ` Eduardo Ochs
2022-12-16 13:39   ` Jean Louis [this message]
2022-12-16 20:28     ` [SOLVED with eev] " Eduardo Ochs
2022-12-17  0:08     ` Emanuel Berg
2022-12-17 12:44       ` Eduardo Ochs
2022-12-18  6:58         ` Jean Louis
2022-12-18  7:51           ` Eduardo Ochs
2022-12-19 17:44 ` Vagn Johansen
2022-12-19 19:19   ` Marcin Borkowski
2022-12-19 21:22     ` Vagn Johansen
2022-12-19 22:15       ` Emanuel Berg
2022-12-20  6:02       ` Marcin Borkowski
2022-12-19 20:34   ` Emanuel Berg
2022-12-19 22:33   ` Jean Louis

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=Y5x1AG7H8AnD1eK7@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=eduardoochs@gmail.com \
    --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).