Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kernel code reading environment #58

Closed
evopen opened this issue Jun 23, 2018 · 1 comment
Closed

Kernel code reading environment #58

evopen opened this issue Jun 23, 2018 · 1 comment

Comments

@evopen
Copy link
Contributor

evopen commented Jun 23, 2018

Hey I'm wondering is there any recommendations for reading (editing) kernel source code.

I know this is a personal preference thing. But I still would like to get some opinions.

I have been using emacs for the last two years in terminal. C/S mode is making it super fast which is better than vim. Clion is amazing but sadly it doesn't support Makefile.

I know a Android kernel developer. His kernel is good(at least I think so) and he's productive(based on commit history). And he told me that he uses vscode.
Hum... I don't know... vscode doesn't even have built-in asm highlighting.

I switched to vim from spacemacs a month ago. But frankly they are the same in general that they rely on gtags and cscope. And I feel lag reading and jumping around function calls.

What about QT Creator? I haven't tried it.

@s-matyukevich
Copy link
Owner

I use vim + cscope + some plugins like NerdTree, thought I'am not quite happy with the cscope experience when searching for symbol usage, symbol definition, etc. A lot of times I have to rely on grep and complicated regexp expressions. It would be nice if somebody can share a better way of working with kernel source.

@evopen evopen closed this as completed Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants