Leonid Podolny <[EMAIL PROTECTED]> writes:
> Bottom line: I'd like to ask all the kernel gurus out there to describe
> their kernel hacking environment -- editor, code browsing plug-in,
> general tips, etc.
While not qualifying for the "guru" title, I use xemacs (no flames,
please!) with etags/g
Leonid Podolny <[EMAIL PROTECTED]> writes:
> Bottom line: I'd like to ask all the kernel gurus out there to describe
> their kernel hacking environment -- editor, code browsing plug-in,
> general tips, etc.
While not qualifying for the "guru" title, I use xemacs (no flames,
please!) with etags/gt
I'm no kernel guru, but I, too, found cscope to be *very* annoying. vim+ctags is much better. (Let alone faster.)
Doing :tag ssize_t or :tag size_t (Or Ctrl+] over the tag itself) will jump to include/linux/types.h without too much fuss.
*However* if you you're looking for tag reference (E.g. a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Disclaimer: I don't want to start a flame war.
Hi, list.
Recently I came to the conclusion that the way that I work with kernel
code is inefficient, and I spend too much time looking for a needed
piece of code.
I work with vim and cscope, but cscope i
