There isn't one. Use the HOWTOs, the FAQs, the info pages, the READMEs, and the man pages. Check in/usr/doc/packagename on a Red Hat system for other package-specific info (though it's not always all included, more's the pity). Then go talk to google and see what it turns up.
The HOWTOs and man pages are invaluable, though. Use them.
I touch type at about 60words/minute on a qwerty and only about 20 on the twiddler, but when I'm writing code the speed difference is much slower. It helps relieve RSI, keeps a hand free for the white board, and lets you stand and move a bit while you type.
ctags stopped cutting it when I moved from C to C++, and it's useless for Java
Exuberant ctags is far advanced over old ctags programs. The C support is much improved and C++ and Java support have been added and work like a charm. Works especially well in combination with Vim. If you don't like the way it handles Java, you can give JTags a try, but it's nowhere near as stable.
If you're doing Java development, you'll probably also want to use Jikes, as it integrates very nicely with QuickFix mode in Vim and make mode in Emacs. There's also a Jikes Debugger java debugger, but I've not used it.
a decent code beautifier, since indent doesn't work right for Java
jsbeautifier is one of many -- a search I did a few months ago turned up 10 or 12 beautifiers for Java, and even more for other languages.
Of course, if you want a good graphical debugger then ddd is the way to go -- it lets you get to the gdb command line if need be.
I was wondering what is the proper procedure for like maybe submitting it?
Send it to the kernel mailing list. If it's not trivial, ask for testers; once it's tested, send again with an explanation and a request for inclusion and CC whoever is the maintainer for that code (looking in MAINTAINERS, hedrick at astro.dyer.vanderbilt dot edu seems like a good choice). Allow a week; if there's no response, send on to Linus and Alan with a brief note of explanation.
Slashdot Mirror
There isn't one. Use the HOWTOs, the FAQs, the info pages, the READMEs, and the man pages. Check in /usr/doc/packagename on a Red Hat system for other package-specific info (though it's not always all included, more's the pity). Then go talk to google and see what it turns up.
The HOWTOs and man pages are invaluable, though. Use them.
I've got a twiddler. It's awesome. I love it.
I touch type at about 60words/minute on a qwerty and only about 20 on the twiddler, but when I'm writing code the speed difference is much slower. It helps relieve RSI, keeps a hand free for the white board, and lets you stand and move a bit while you type.
ctags stopped cutting it when I moved from C to C++, and it's useless for Java
Exuberant ctags is far advanced over old ctags programs. The C support is much improved and C++ and Java support have been added and work like a charm. Works especially well in combination with Vim. If you don't like the way it handles Java, you can give JTags a try, but it's nowhere near as stable.
If you're doing Java development, you'll probably also want to use Jikes, as it integrates very nicely with QuickFix mode in Vim and make mode in Emacs. There's also a Jikes Debugger java debugger, but I've not used it.
a decent code beautifier, since indent doesn't work right for Java
jsbeautifier is one of many -- a search I did a few months ago turned up 10 or 12 beautifiers for Java, and even more for other languages.
Of course, if you want a good graphical debugger then ddd is the way to go -- it lets you get to the gdb command line if need be.
Sumner
Send it to the kernel mailing list. If it's not trivial, ask for testers; once it's tested, send again with an explanation and a request for inclusion and CC whoever is the maintainer for that code (looking in MAINTAINERS, hedrick at astro.dyer.vanderbilt dot edu seems like a good choice). Allow a week; if there's no response, send on to Linus and Alan with a brief note of explanation.
Revise and repeat as needed.
Sumner