From: Eduardo Ochs <eduardoochs@gmail.com>
To: Eduardo Ochs <eduardoochs@gmail.com>,
Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: [SOLVED with eev] Re: How to quicker jump to function definition than C-h k ?
Date: Fri, 16 Dec 2022 17:28:14 -0300 [thread overview]
Message-ID: <CADs++6h2m1RMsu2w1VkP0Wk21Ue1d6ikxrJP_oupPBgiE72=Aw@mail.gmail.com> (raw)
In-Reply-To: <Y5x1AG7H8AnD1eK7@protected.localdomain>
On Fri, 16 Dec 2022 at 11:45, Jean Louis <bugs@gnu.support> wrote:
>
> * 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.
Great! Thanks for the feedback! =)
I try to make the functions and features of eev as composable as
possible - in this sense -
https://lambdaland.org/posts/2022-11-07_unix_philosophy/
and
(find-efunction 'right-char)
does _a part_ of what happens when we type `M-h k <right>' and we
click on the link that goes to the source code. I remember vaguely
that I struggled a log in the 90s to discover how to go to the source
without clicking on a button...
Cheers =),
Eduardo Ochs
http://angg.twu.net/#eev
http://angg.twu.net/eepitch.html
next prev parent reply other threads:[~2022-12-16 20:28 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 ` [SOLVED with eev] " Jean Louis
2022-12-16 20:28 ` Eduardo Ochs [this message]
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='CADs++6h2m1RMsu2w1VkP0Wk21Ue1d6ikxrJP_oupPBgiE72=Aw@mail.gmail.com' \
--to=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).