Re: how to look for source code in kernel

[Jesper Juhl]

On Fri, 28 Dec 2012, Guennadi Liakhovetski wrote:

> On Fri, 28 Dec 2012, Borislav Petkov wrote:
> 
> > On Thu, Dec 27, 2012 at 11:36:13PM -0800, Eric W. Biederman wrote:
> > > git-ls-files | xargs fgrep 'struct f2fs_inode'
> > > 
> > > That returns instantly and tells me where to look.  If you can do an
> > > instant brute force search what is the point of an index?
> > 
> > Not if you're using a lame-ass laptop with a rotating disk:
> > 
> > $ time git ls-files | xargs grep -E 'struct mce\W*{'
> > arch/x86/include/uapi/asm/mce.h:struct mce {
> > arch/x86/kernel/cpu/mcheck/mce.c:               if (!final || memcmp(m, final, sizeof(struct mce))) {
> > 
> > real    2m48.415s
> > user    0m2.388s
> > sys     0m15.668s
> > 
> > What I've grown accustomed to is cscope with a prior find run on the
> > kernel source tree to create a custom cscope.files which cscope uses to
> > index and then using vim bindings in cscope so that if, for example, the
> > cursor is on a function call, executing a keyboard shortcut opens the
> > definition of that function in another vim tab. I.e., a thin IDE done
> > right.
> 
> ...same works with TAGS under emacs, the only annoying problem with it 
> since "recently" (about half a year or more) is that "make TAGS" is 
> spewing out tons of
> 
> etags: Unmatched ( or \( while compiling pattern
> 
> oh well, looks like noone is using it / noone cares enough...
> 
I use it. I haven't bothered (yet) to look into the cause of the message 
it spews since the etags ('TAGS') file it produces still seems to work 
well enough.

-- 
Jesper Juhl <jj@xxxxxxxxxxxxx>       http://www.chaosbits.net/
Don't top-post http://www.catb.org/jargon/html/T/top-post.html
Plain text mails only, please.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/