From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Non-web based LXR
Date: Tue, 31 Oct 2017 13:14:30 +1100 [thread overview]
Message-ID: <20171031021430.GD12341@eros> (raw)
In-Reply-To: <20171030215510.GU12341@eros>
On Tue, Oct 31, 2017 at 08:55:10AM +1100, Tobin C. Harding wrote:
> CC'd Thomas because I read online recently him commenting on web based
> cross reference tools.
>
> Hi,
>
> Does any one use a terminal based source code cross referencer to search
> the kernel tree?
>
> thanks,
> Tobin.
Responding to all responses in single email. Thanks for the
responses. Apologies, I need to learn to be more explicit when asking
questions to be more respectful of other peoples time.
I already use grep (various versions, git grep, egreg, and ack).
I also already use ctags in emacs (or is it called etags when in emacs).
I [too] often still find myself going to
http://elixir.free-electrons.com
I just attempted to recreate an example search that fails using grep or
ctags but was unable to. Perhaps the problem is a user error, i.e I come
across a code search that is not fully serviced by grep/ctags, go to
free-electros, then go back to it from habit only later realizing that I
am doing so when I get annoyed with having to use a web browser.
So, thank you for your ideas. I'll consider this issue resolved by;
Use git grep
Use ctags/etags
Use free-electrons as a last resort
thanks,
Tobin.
next prev parent reply other threads:[~2017-10-31 2:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 21:55 Non-web based LXR Tobin C. Harding
2017-10-30 23:26 ` valdis.kletnieks at vt.edu
2017-10-31 0:44 ` Rob Rennison
2017-10-31 2:14 ` Tobin C. Harding [this message]
2017-10-31 9:53 ` François
2017-10-31 14:59 ` Mike Harless
2017-11-01 0:13 ` Tobin C. Harding
2017-11-02 14:31 ` Mike Harless
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=20171031021430.GD12341@eros \
--to=me@tobin.cc \
--cc=kernelnewbies@lists.kernelnewbies.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 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.