mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ramagudi Naziir <naziirr@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: how do YOU hack the linux kernel ?
Date: Tue, 19 Jan 2010 14:52:57 +0200	[thread overview]
Message-ID: <dfb262381001190452k3bad790ax14bbdbe92210b2d3@mail.gmail.com> (raw)

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.
You can also ":tabnew ." and just browse the folders, but that's super slow too.


so, do you use stuff like 'Source Insight' ?

It does have a great files viewer, where you can just type a few
letters, and it immediately shows only files that match the pattern
you typed (just like in iTunes). This is blazing fast. But it's Source
Insight. you need to fight it not to over-visualizes your file, and
not to mess up with your whitespace. not to mention that it's
windows-only (although wine seems to help here a bit).


so.. back to vim ? It does have relevant plugins that tries to give
you fast files opener, like the 'project' plugin (totally unmaintained
and buggy) or the 'tselectfiles' plugin (slow, hard to use).


I'd really like to use vim, it's fast and gives you control, but
really I must have some way to quickly access my files.


Any ideas ?

             reply	other threads:[~2010-01-19 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 12:52 Ramagudi Naziir [this message]
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
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=dfb262381001190452k3bad790ax14bbdbe92210b2d3@mail.gmail.com \
    --to=naziirr@gmail.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®