On 11/08/07, Ramagudi Naziir <naziirr@xxxxxxxxx> wrote: > hi all > > i'm interested to find the best environment for kernel hacking. > > plain vi ? i like vi a lot but i find it hard to navigate in large projects. > maybe there are some features i am not aware of... I would say you don't know about "tags". If you run "make tags" in your kernel source dir, then you'll have an index that lets you follow "tags" easily in many editors. What this means is that if you place the cursor on a function name you can jump to the definition with a keypress and back again with another (even when the definition is in a different file). For example, in 'vim' you can use these : :ta tag Find a tag. Ctrl-] Find the tag under the cursor. Ctrl-T Return to previous location before jump to tag Many other editors can be used as well in similar ways. This makes it a bit easier to navigate the source. You can also use "make cscope" to generate a cscope index (http://cscope.sourceforge.net/) > (currently if i see a function/macro i need, i grep for it and then > open its file > with the vi e cmd) > You also have the kerneldoc documentation which you can get at by running "make mandocs", "make xmldocs", "make pdfdocs" etc... see "make help" for more. > what do you suggest ? how do YOU hack your kernel ? > Most of the time I simply use plain vim, (e)grep, find, awk, etc to find what I need and edit the source. Tools such as lxr (http://lxr.linux.no/) also often come in handy. git is also a fantastic tool to see what has changed recently, who edited a file last etc. If you are not already using git I would suggest you start reading up on it. -- Jesper Juhl <jesper.juhl@xxxxxxxxx> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
