From: Drew Adams <drew.adams@oracle.com>
To: Wilfred Hughes <me@wilfred.me.uk>, emacs-devel <emacs-devel@gnu.org>
Subject: RE: [Ann] elisp-refs, a semantic elisp search tool (GNU ELPA request)
Date: Fri, 14 Oct 2016 20:38:28 -0700 (PDT) [thread overview]
Message-ID: <a7bcb9ba-d1ae-4a4a-96b4-d0fdae340468@default> (raw)
In-Reply-To: <CAFXAjY6rXhYi5mKPxtfg7371u51F-ZaP4H=n0s7iaG8_JsCFig@mail.gmail.com>
Sounds interesting.
> semantic search of all the elisp in the current Emacs instance.
When I read that, I thought you meant the code in all _loaded_
Lisp libraries.
> parsing all the code on `load-path',
But this seems to be something entirely different - all the
code on disk under all the directories in `load-path'.
I don't see why someone would want to do the latter, instead
of the former. I, for one, have tons of stuff on my `load-path'
that I rarely, if ever, load/use. My `load-path' is just a
way to tell Emacs where to look for a library IF I should
happen to ask for it.
A quick look at the code suggests that you do in fact mean
the former. In that case, better not speak of "load path".
What you are talking about are the "files that have been
loaded in Emacs", as your `elisp-refs--loaded-files' doc
string says.
next prev parent reply other threads:[~2016-10-15 3:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 3:26 [Ann] elisp-refs, a semantic elisp search tool (GNU ELPA request) Wilfred Hughes
2016-10-15 3:38 ` Drew Adams [this message]
2016-10-15 5:28 ` el-search 1.0 (was: [Ann] elisp-refs, a semantic elisp search tool (GNU ELPA request)) Michael Heerdegen
2016-10-15 6:07 ` [Ann] elisp-refs, a semantic elisp search tool (GNU ELPA request) Eli Zaretskii
2016-10-15 6:09 ` Michael Heerdegen
2016-10-15 14:53 ` raman
2016-10-15 15:30 ` Stefan Monnier
2016-10-15 19:25 ` Dmitry Gutov
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=a7bcb9ba-d1ae-4a4a-96b4-d0fdae340468@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=me@wilfred.me.uk \
/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.