Developing environments used for kernel development
My boss came to my desk today raiging that I should use more productive tools for developing. Well I don't want to begin an editor war but, yes, I use emacs. I used to use vim before but the integration of emacs and gdb has caught my attention. To be clear, as "more productive tools" he understands graphical eye candy tools. My argument to use an "simple editor plus makefiles" was, it just works and thats it. So before to downloading eclipse just to make my boss's eyes happy I've decided to make a little research. What you guys are using today to develope kenrel code? Best Regards, - dhs -- *"Do or do not. There is no try"* *Yoda Master*
On Tue, Dec 22, 2015 at 11:27 AM, Daniel. <danielhilst@gmail.com> wrote:
My boss came to my desk today raiging that I should use more productive tools for developing. Well I don't want to begin an editor war but, yes, I use emacs. I used to use vim before but the integration of emacs and gdb has caught my attention.
To be clear, as "more productive tools" he understands graphical eye candy tools. My argument to use an "simple editor plus makefiles" was, it just works and thats it. So before to downloading eclipse just to make my boss's eyes happy I've decided to make a little research.
What you guys are using today to develope kenrel code?
While in virtual console, I use midnight commander's built in editor for the bulk of my actual dev work. Then when I need to email anything, I switch to gui and use gedit to open the file, copy it to the clipboard, and paste it into my email client for patch delivery. My criteria is "hold the text and stay the hell out of my way. Be a tool and don't try to do my thinking for me."
Best Regards, - dhs
-- "Do or do not. There is no try" Yoda Master
Is there anybody using cscope inside vim? Is there an alternative keybinds for the :cs commands? Regards, - dhs 2015-12-25 15:14 GMT-02:00 Raymond Jennings <shentino@gmail.com>:
On Tue, Dec 22, 2015 at 11:27 AM, Daniel. <danielhilst@gmail.com> wrote:
My boss came to my desk today raiging that I should use more productive tools for developing. Well I don't want to begin an editor war but, yes, I use emacs. I used to use vim before but the integration of emacs and gdb has caught my attention.
To be clear, as "more productive tools" he understands graphical eye candy tools. My argument to use an "simple editor plus makefiles" was, it just works and thats it. So before to downloading eclipse just to make my boss's eyes happy I've decided to make a little research.
What you guys are using today to develope kenrel code?
While in virtual console, I use midnight commander's built in editor for the bulk of my actual dev work.
Then when I need to email anything, I switch to gui and use gedit to open the file, copy it to the clipboard, and paste it into my email client for patch delivery.
My criteria is "hold the text and stay the hell out of my way. Be a tool and don't try to do my thinking for me."
Best Regards, - dhs
-- "Do or do not. There is no try" Yoda Master
-- "Do or do not. There is no try" Yoda Master
Hi, On 28/12/2015 13:28, Daniel. wrote:
Is there anybody using cscope inside vim? Is there an alternative keybinds for the :cs commands?
I use this file from the cscope distribution, that defines normal mode bindings: http://cscope.sourceforge.net/cscope_maps.vim Regards, Manuel
El 28/12/2015 13:58, "Manuel Pégourié-Gonnard" <mpg@elzevir.fr> escribió:
Hi,
On 28/12/2015 13:28, Daniel. wrote:
Is there anybody using cscope inside vim? Is there an alternative keybinds for the :cs commands?
I use this file from the cscope distribution, that defines normal mode bindings:
They're also available in the cscope help inside Vim. Once you get used to them they're extremely useful, a real productivity booster, specially for big projects.
Regards, Manuel
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
This is fun: http://vimdoc.sourceforge.net/htmldoc/usr_41.html#script :D 2015-12-28 12:05 GMT-02:00 Fernando Apesteguía <fernando.apesteguia@gmail.com>:
El 28/12/2015 13:58, "Manuel Pégourié-Gonnard" <mpg@elzevir.fr> escribió:
Hi,
On 28/12/2015 13:28, Daniel. wrote:
Is there anybody using cscope inside vim? Is there an alternative keybinds for the :cs commands?
I use this file from the cscope distribution, that defines normal mode bindings:
They're also available in the cscope help inside Vim. Once you get used to them they're extremely useful, a real productivity booster, specially for big projects.
Regards, Manuel
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- "Do or do not. There is no try" Yoda Master
Well I found something that I use frequently on emacs and can't find an alternative for vim. While visiting an .patch (or .diff) file from emacs I can jump to the position of file just by pressing enter. I just can't find something like this on vim. When developing I like to review my changes before commit, doing little tweaks like removing empty new lines and trailing whitespaces. On emacs I can get an diff from the version control with C-x v =, then doing the fixes for creating a nice patch, doing C-x v = will refresh the diff window, so I do this until I think that is good enough. While I can get a diff from file with %!git diff % at vim, I can't jump to modification on file directly from the patch window. Any ideas on how to achieve this? Regards, 2015-12-28 17:11 GMT-02:00 Daniel. <danielhilst@gmail.com>:
This is fun: http://vimdoc.sourceforge.net/htmldoc/usr_41.html#script :D
2015-12-28 12:05 GMT-02:00 Fernando Apesteguía <fernando.apesteguia@gmail.com>:
El 28/12/2015 13:58, "Manuel Pégourié-Gonnard" <mpg@elzevir.fr> escribió:
Hi,
On 28/12/2015 13:28, Daniel. wrote:
Is there anybody using cscope inside vim? Is there an alternative keybinds for the :cs commands?
I use this file from the cscope distribution, that defines normal mode bindings:
They're also available in the cscope help inside Vim. Once you get used to them they're extremely useful, a real productivity booster, specially for big projects.
Regards, Manuel
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- "Do or do not. There is no try" Yoda Master
-- "Do or do not. There is no try" Yoda Master
On 29/12/2015 06:10, Daniel. wrote:
Well I found something that I use frequently on emacs and can't find an alternative for vim. While visiting an .patch (or .diff) file from emacs I can jump to the position of file just by pressing enter. I just can't find something like this on vim.
I don't know how to do this with vim either. The ftplugin/diff.vim file from the vim runtime distribution doesn't have any such magic.
When developing I like to review my changes before commit, doing little tweaks like removing empty new lines and trailing whitespaces. On emacs I can get an diff from the version control with C-x v =, then doing the fixes for creating a nice patch, doing C-x v = will refresh the diff window, so I do this until I think that is good enough.
What I use for that purpose in vim is the :Gdiff command provided by the fugitive plugin. It splits your window between the checked out version of your file and the version in the git index. In addition to reviewing changes, it's also extremely useful for partial commits when you got carried away during your editing and made an unrelated change: you can move just the part you want to the index, then commit that, then commit the rest. Or if you made a change you want to revert without losing your other changes. The usual shortcuts from vimdiff mode are available to move things between the index and the checkout: do, dp (diff other, diff push) and ]c [c for navigating the changes. Manuel.
participants (4)
-
Daniel. -
Fernando Apesteguía -
Manuel Pégourié-Gonnard -
Raymond Jennings