This repo contains Exported Jar of my Intellij IDEA settings. (Editor preferences, Keymaps and so on) In addition there are the descriptions of my key map which I have set to enhance productivity. This is meant to be a reference for me. Collaboration and suggestions are welcome
Usage: Download settings.jar file and follow: Imorting Settings Exporting Settings
Some Useful Resources:
Java and Android IntelliJ Wizardry Lite with Heinz Kabutz (Free at Udemy)
Vojtech Ruzicka's Programming Blog (on Intellij Productivity)
Intellij Feature Trainer plugin
Scripted Extensions
We can use scripted extension for achieving various mundane repeatitive tasks. Lets take example of creating pojo from each db table. Included in this repo is a file generate_pojos.groovy
. Place it inside Scratches and Consoles->Extensions->Database Tools and SQL->Schema
. Right click on table name in DB view, choose script, choose directory location and save. Modify the groovy script to change package name.
We can have as many groovy scripts as we would like to have. Personally I have found this approach easier to do scripting tasks like file creation (mostly model pojo, repository, etc)
Key ShortCut | Action |
---|---|
Windows+D | Toggle distraction free mode (hides all the toolbars, just code window is displayed) |
Windows+F | Toggle Full screen mode |
Alt+Left Arrow | Navigate back (useful while debugging (stepping in deeper into methods/classes) |
Alt+Right Arrow | Navigate forward |
F2 | Jump to (next) Error |
Alt-Enter | '\r' carriage return (when cursor is not necessarily at the line-end) |
#Commonly Used Operations
1. Regex Search for multiple words: (word1).*(word2)|\2.*\1
Debugging/Changing Values Dynamically:
Toggling distraction-free/full-screen mode:
Git Blame
git blame
is a command which shows the contributor to a particular file line by line. Using it in terminal is fairly easy: git blame $filename
. In Intellij we can set root for the VCS (Version control system). Now git blame
translates to Annotations
under VCS->Git and it displays line by line contributor in a nice formatted way. This can be very useful when working in a large project or dealing with merge conflicts.
Share Run/Debug Configurations When working on large projects with a lot of dependencies and configuration details it can be PITA just to set up and configure your project. You can share the run/debug configuration to solve this.