From: "Daniel Martín" <mardani29@yahoo.es>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Check/find/locate the customized function/command of a specific project in Emacs conveniently/quickly/efficiently.
Date: Mon, 05 Jul 2021 23:32:54 +0200 [thread overview]
Message-ID: <m1fswssayh.fsf@yahoo.es> (raw)
In-Reply-To: <CAGP6POKG-Hmsxbs+8NC6jQyrGGBPMFf8-DgeZqd-cQAowjzodQ@mail.gmail.com> (Hongyi Zhao's message of "Mon, 5 Jul 2021 09:57:47 +0800")
Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>>
>> It seems like use-package! is a macro defined by Doom Emacs, so you can
>> do C-h f use-package! RET to read its documentation. Similarly,
>> +latex-symbols-company-backend seems like a Lisp variable added by Doom
>> Emacs, so you can get help by doing C-h v +latex-symbols-company-backend
>> RET.
>>
>> Alternatively, you can type C-h o (describe-symbol) to get documentation
>> about any symbol (variable, function, etc.).
>
> To use the above method, I must have installed Doom Emacs, but that's
> not the case on my side - I just want to inspect Doom Emacs'
> configurations source code for learning some mechanisms developed by
> it.
In that case, as the ELisp code is not part of the environment, you
could try any of the following features:
- Create a TAGS file for the files in the Doom project. Read (info
"(emacs) Tags Tables") for more information.
- M-x grep or M-x rgrep to use grep or a similar tool to search for
a regular expression.
- If you want something a bit more sophisticated that understands ELisp
better, you could try the ELPA package el-search
(https://elpa.gnu.org/packages/el-search.html).
prev parent reply other threads:[~2021-07-05 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 2:42 Check/find/locate the customized function/command of a specific project in Emacs conveniently/quickly/efficiently Hongyi Zhao
2021-07-04 21:22 ` Daniel Martín
2021-07-05 1:57 ` Hongyi Zhao
2021-07-05 21:32 ` Daniel Martín [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
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=m1fswssayh.fsf@yahoo.es \
--to=mardani29@yahoo.es \
--cc=help-gnu-emacs@gnu.org \
--cc=hongyi.zhao@gmail.com \
/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).