Day three of my brand new job - woohoo! One of my first tasks is checking the documentation
of IntelliJ, since I’m
already a “Power User”, to see if there’s stuff missing that someone like me might want to see. Firstly, a confession -
I’m not sure I’ve actually read the IntelliJ documentation before. I mean, really read it. Of course, I’ve dipped
into it when I needed to know something, I’ve searched for help with specific items, but like many developers, I tend to
use something first rather than read the documentation first.
But I’ll tell you what, today I’ve learnt a whole bunch of useful things IntelliJ can do that I hadn’t previously known,
and they’re the sorts of things you would only stumble over if a) you read the docs (pah!) or b) you watched someone
else using the tool and saw them doing something you didn’t know was possible.
So here’s today’s list, and feel free to laugh at me and be smug in my direction if you already knew these things (note: I
have upgraded to IntelliJ 14, and at the time of writing I don’t know which of these features are new and which are
simply previously undiscovered):
Navigate directly to an action or option
Press Shift+Ctrl+A (Windows) or Shift+Cmd+A (Mac) and start typing the name of the thing you want to do, or the setting
you want to change. I’ve found this especially useful now I’m back on Windows and I don’t have that nice helpful typing
box on the help menu that will take me straight to the menu item I want. But what’s most useful about this for me today,
as I’m setting up a new profile on a new laptop (more on the new laptop later, if it doesn’t defeat me utterly) is that
from here, you can turn various settings on and off without having to navigate through the settings screen:
I never knew there was a
shortcut for finishing off a statement,
all that Java boilerplate you need to keep the compiler happy - semi colons and curly brackets and everything. But
there is, and I can see it being super useful, especially if you’re using other bits of IntelliJ code completion to
create the core of your line of code.
Issue tracker integration
I’m sure loads of people are already using integration with their favourite issue tracker, but I hadn’t really thought
about this as something that I really cared about. But I was watching the intro videos for YouTrack (not surprisingly
I’ll be using this instead of Jira during my time at JetBrains) and when I saw
how the IDE integration worked, I
suddenly realised how this small thing can add up to save thousands of keystrokes over time, not to mention saving
precious navigational seconds and window-switching.
For me, just the ability to generate at least the start of the commit message is a saving in time, and adds to project
consistency if all your developers are doing the same thing. On my last project we only just realised we all quoted the
Jira issues in subtly different ways.
Settings shortcut keys
When I initially started using IntelliJ in anger back in 2008, I was very much a point-and-click type user. Over time,
pair programming with keyboard-super-users and giving live demos with very limited time available, I’ve worked harder
to become a keyboard-shortcuts person. With the latest version of IntelliJ, I can’t find the tiny icons I use to get to
the settings window, something that I’ve been using a lot as I set up the new IDE instance on the new laptop. So I bit
the bullet and learnt the keyboard shortcuts, and it’s already saving me a bunch of time (on the rare occasions when the
aforementioned “Navigate to Action” fails me).
Ctrl+Alt+S for the settings dialog (appears to be Cmd + , on the Mac)
Shift+Ctrl+Alt+S for the project structure dialog (appears to be Cmd + ; on the Mac)
Yeah. I can’t believe I wasn’t already using those either.
Selecting the negative
I use completion/suggestions all the time from IntelliJ, I’m far too lazy to type everything. What I didn’t realise, is
that you don’t just have to accept the default they give you. If, for example, IntelliJ suggests a boolean value, you
can get it to negate that value by selecting it with “!” instead of enter or tab. Yes, I know I’ve done a horrible job
of explaining that, but take a look at
and try it, it’s quite cool.
Exclude from Autocomplete
Speaking of code completion, sometimes IntelliJ is sometimes just a bit too keen to suggest something, and you really
will never want that value. In the past, I’ve always used
Settings -> Editor -> General -> Auto Import to manage the
suggestions (the most common one for me is I will never want
java.awt.List, I will almost always want
java.util.List). Well, you don’t have to go into settings to do this, you can
do it from the suggestions themselves -
navigate to the item you don’t want (in my case,
java.awt.List) and press Alt+Enter, this will give you the option
of excluding this from the suggestions in the future.
That’s what I found from just one day of browsing the documentation and setting up my IDE from scratch yet again.
Maybe I’ll promptly forget all these, or maybe they’ll be new weapons in my armoury of IDE-fu. Either way, maybe one or
two people will find this useful.