Go to the Project Explorer or Package Explorer View and click on the Link to Editor button If you take vertical packaging approach, which holds classes together based on functionality rather than on layers (dao, service etc.), which I highly recommend, this comes pretty handy. What does it do? Whenever I edit a file it diplays it instantly in the package explorer/project. For example ff it is a class usually, I also work on others classes in the same package – you can quickly navigate to the other class in the package by having the Link to Editor feature turned on. I often find myself when editing a file and to need to edit others files in the same context.
Run as JUnit Test (valid both for test classes and methods) Quickly move between methods in the editor add curly braces)įind usage of class/variable in workspace / project Source (Generate getters/setters, constructor etc.)Ĭtrl+M (works for any current view with focus on)Ĭomplete current statement such as if, do-while, try-catch, return (or a method call) into a syntactically correct construct (e.g. “PoDI” will also list the Podcast Dao Impl class)įile Structure pop-up for quick navigation through the current file (members, methods) (in both cases you can ease the search by filtering the lookup list with the help of the “camel words” prefixes e.g. Here’s a list of the shortcuts I use or ought to be using the most: Description Show javadoc when hovering with the mouse.NOTE: I've also run into issues where in Citrix (remote desktop environment for windows) or using different Window Manager's in Linux that different keys that you might want to use (like Alt+RightArrow) don't work because another app "eats" that key combination so the IDE never even sees that that key was pressed. I don't see that coming anytime soon, unless I write it. I want an application that lets me define the key bindings I want to use and then configures the applications to use those key bindings. I'm not seeing any wonderful answers, and mine isn't one either! I was just searching for another solution to this when I saw your post. It's a great idea in concept but I and others have had issues with it. NOTE: I tried using IntelliJ's Settings Repository and that helped some (if you're not aware if it, it lets you sync IntelliJ settings in GITHUB and then when you change settings they are synced with the repo, and when you get to the next system, those changes are merged).
When I get to a new machine I download them and configure them on the new machine. It's a bit of a pain, but it is what I do.Įxport the key bindings for each tool and save them to a file that is stored in GITHUB. I keep: "what I want to do", tool/keybinding/commandname, default command name (for that key binding) for each of the tools. I have a MS Word document with the different tools and the key bindings I use for them. This is somehow still natural (probably I've used emacs for 30 years).
I've come to use the windows cut/copy/paste, undo/redo which for better or worse seems to be the default for most systems except emacs (so that's easy for them). So the basic's of navigation (up,down,left,right,home,end) all work the same. I currently use emacs key bindings for: emacs, eclipse, Microsoft Word, IntelliJ, Sublime, and vscode. I have a primary set of key bindings that I use across every one that will allow me to change my key bindings. I have used vi, emacs, vim, notepad++, eclipse, Microsoft Word, Visual Studio, IntelliJ, Chrome Debugger, Atom, Sublime, and most recently VSCode.
:-) Nowadays, vim can do most everything, but Eclipse, IntelliJ, and Visual Studio are widely used. It used to be simple because emacs could do everything. My approach has changed over the years (30+ in this field).