From: Eduardo Ochs <eduardoochs@gmail.com>
To: Eduardo Ochs <eduardoochs@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: [SOLVED with eev] Re: How to quicker jump to function definition than C-h k ?
Date: Sun, 18 Dec 2022 04:51:58 -0300 [thread overview]
Message-ID: <CADs++6hhWFKRX=1RsNBtVC401kJGZs76SJoJBOSyBnqF6SzV7g@mail.gmail.com> (raw)
In-Reply-To: <Y566CEQusrY/pxuu@protected.localdomain>
On Sun, 18 Dec 2022 at 04:28, Jean Louis <bugs@gnu.support> wrote:
>
> * Eduardo Ochs <eduardoochs@gmail.com> [2022-12-17 15:46]:
> > It's in eev, obviously! =)
> > You can find its source with:
> >
> > (find-efunction 'find-efunction)
>
> Me I am using eev from time to time, so it works. Though it would be
> better to have such function liberated from larger package.
Hi Jean Louis,
It should be easy to copy it and its dependencies - they're very few -
to your init files. But note that to run it you only need to have eev
"loaded", not "activated"... this distinction is explained in these
two sections:
(find-eev-quick-intro "1. Installing eev" "does NOT activate")
(find-eev-install-intro "0. Loading eev")
http://angg.twu.net/eev-intros/find-eev-quick-intro.html#1
http://angg.twu.net/eev-intros/find-eev-install-intro.html#0
Cheers,
Eduardo
next prev parent reply other threads:[~2022-12-18 7:51 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
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 [this message]
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++6hhWFKRX=1RsNBtVC401kJGZs76SJoJBOSyBnqF6SzV7g@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).