From: Andi Kleen <andi@firstfloor.org>
To: Ramagudi Naziir <naziirr@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how do YOU hack the linux kernel ?
Date: Thu, 21 Jan 2010 01:15:05 +0100 [thread overview]
Message-ID: <87ocko2u0m.fsf@basil.nowhere.org> (raw)
In-Reply-To: <dfb262381001190452k3bad790ax14bbdbe92210b2d3@mail.gmail.com> (Ramagudi Naziir's message of "Tue, 19 Jan 2010 14:52:57 +0200")
Ramagudi Naziir <naziirr@gmail.com> writes:
> do you use vim ?
>
> If so, how do you open files you want to read/edit ?
> Assuming you don't remember their exact name/location, you'd need to
> use something like 'find . -iname '*pattern*'. which is slow.
GNU id-utils does that nicely (file name / symbol lookup)
I usually use it for symbol lookup.
I am not aware of a vim integration though, although
there's one for emacs.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-01-21 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 12:52 how do YOU hack the linux kernel ? Ramagudi Naziir
2010-01-19 13:15 ` Samuel Thibault
2010-01-19 14:29 ` Américo Wang
2010-01-20 6:35 ` Petr Uzel
2010-01-20 8:33 ` Michael Wookey
2010-01-20 18:04 ` Krzysztof Halasa
2010-01-21 0:15 ` Andi Kleen [this message]
2010-01-29 8:10 ` Daniel Mack
2010-01-29 11:37 ` Andy Walls
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=87ocko2u0m.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naziirr@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