IntelliJ IDEA – Gems you can find inside

Posted on 2016/05/01 by devmake

This is an opinionated very short list of features that I find useful or interesting in IntelliJ up to version 14.1.

IntelliJ IDEA – Gems you can find inside from devmilan

Switching git branches faster on command line

Posted on 2016/04/21 by devmake

I first started with an alias in my .bash_profile

alias b='git branch'
alias gco='git checkout'

1 2	alias b='git branch' alias gco='git checkout'

The drawback was that although it is shorter, it doesn’t give you suggestions based on existing branches when pressing “tab” (same as unix commands work for folders/files). Git checkout command does.

So I created an alias to checkout develop.

alias gcd='git checkout develop'

1	alias gcd='git checkout develop'

But I wanted to use it for any branch…

Then I wrote a script (see below) and added another alias

alias gc='/c/APPS/scripts/git/git-checkout-fuzzy.sh'

1	alias gc='/c/APPS/scripts/git/git-checkout-fuzzy.sh'

The script does a git checkout for a first branch that matches the first script argument

gc branchNameOrJustUniquePartOfTheName

1	gc branchNameOrJustUniquePartOfTheName

Full example:

$ b

* develop

feature/JIRA-123-show-some-analytics

master

$ gc ana

Running /c/APPS/scripts/git/git-checkout-fuzzy.sh with parameter [ana]

Matching branches:

- feature/JIRA-123-show-some-analytics

Checking out feature/JIRA-123-show-some-analytics

Switched to branch 'feature/JIRA-123-show-some-analytics'

Your branch is up-to-date with 'origin/feature/JIRA-123-show-some-analytics'.

$ b

* develop

feature/JIRA-123-show-some-analytics

master

$ gc ana

Running /c/APPS/scripts/git/git-checkout-fuzzy.sh with parameter [ana]

Matching branches:

- feature/JIRA-123-show-some-analytics

Checking out feature/JIRA-123-show-some-analytics

Switched to branch 'feature/JIRA-123-show-some-analytics'

Your branch is up-to-date with 'origin/feature/JIRA-123-show-some-analytics'.

And here is the script – git-checkout-fuzzy.sh:

#!/usr/bin/env bash

# git checkout for first branch that matches the first script argument

echo "Running $0 with parameter [$1]"

PART_OF_BRANCH_NAME=$1

if [ -z "${PART_OF_BRANCH_NAME}" ]; then
    echo "Please pass 1 parameter with part of a branch name"; exit 1;
fi

echo "Matching branches: "  # added "- " as prefix for the list
git for-each-ref --format='- %(refname:short)' refs/heads/ | grep ${PART_OF_BRANCH_NAME}

foundBranchName=`git for-each-ref --format='%(refname:short)' refs/heads/ | grep ${PART_OF_BRANCH_NAME} | head -1`

if [ -z "${foundBranchName}" ]; then
    echo "No matching branch found"; exit 2;
fi

echo "Checking out ${foundBranchName}"
git checkout ${foundBranchName}

#!/usr/bin/env bash

# git checkout for first branch that matches the first script argument

echo "Running $0 with parameter [$1]"

PART_OF_BRANCH_NAME=$1

if [ -z "${PART_OF_BRANCH_NAME}" ]; then

echo "Please pass 1 parameter with part of a branch name"; exit 1;

echo "Matching branches: " # added "- " as prefix for the list

git for-each-ref --format='- %(refname:short)' refs/heads/ | grep ${PART_OF_BRANCH_NAME}

foundBranchName=`git for-each-ref --format='%(refname:short)' refs/heads/ | grep ${PART_OF_BRANCH_NAME} | head -1`

if [ -z "${foundBranchName}" ]; then

echo "No matching branch found"; exit 2;

echo "Checking out ${foundBranchName}"

git checkout ${foundBranchName}

Enjoy and please let me now in the comments below if you find it useful and it works for you.

UPDATE: In IntelliJ it is probably better to set a keyboard shortcut for VCS > Git > Branches…

Switch windows with keyboard on Mac OS X

Posted on 2014/06/23 by devmake

Very nice option to switch windows is Contexts app. It allows you to switch applications using Alt+Number. It provides a sidebar with all running apps and ability to replace Cmd+Tab including smart search through currently opened windows.

However I often prefer to use a keyboard shortcut that doesn’t change – for example Alt+x for XCode and Alt+c for Google Chrome. BetterTouchTool is very handy for this. Just create a keyboard shorcut, use Execute Terminal Command action and put configure it with similar command:

osascript -e 'tell application "Chrome" to activate'

1	osascript -e 'tell application "Chrome" to activate'

XCode – Open file in current tab in external editor (MacVim)

Posted on 2014/03/20 by devmake

I wanted to open the current file from XCode 5 in MacVim similarly as I do in IntelliJ. After some research I found following solution that works for me. If Assistant editor is opened, the file from the Standard Editor (on the left side) is opened regardless which editor is active.

on run {input, parameters}

    set current_document_path to ""

    tell application "Xcode"
        set last_word_in_main_window to (word -1 of (get name of window 1))
        if (last_word_in_main_window is "Edited") then
            display notification "Please save the current document and try again"
            -- eventually we could automatically save the document when this becomes annoying
        else
            set current_document to document 1 whose name ends with last_word_in_main_window
            set current_document_path to path of current_document
        end if
    end tell

    tell application "MacVim"
        if (current_document_path is not "") then
            activate
            open current_document_path
        end if
    end tell

    return input
end run

on run {input, parameters}

set current_document_path to ""

tell application "Xcode"

set last_word_in_main_window to (word -1 of (get name of window 1))

if (last_word_in_main_window is "Edited") then

display notification "Please save the current document and try again"

-- eventually we could automatically save the document when this becomes annoying

else

set current_document to document 1 whose name ends with last_word_in_main_window

set current_document_path to path of current_document

end if

end tell

tell application "MacVim"

if (current_document_path is not "") then

activate

open current_document_path

end if

end tell

return input

end run

First raised as a StackOverflow question.

Update: In case you were wondering how to start MacVim from XCode, you should maybe try XVim instead. It brings Vim mode right into XCode.

Kill all application windows

Posted on 2013/11/06 by devmake

As I develop an application in GWT and have IntelliJ set up to open the app in IE when debugging/running it, I end up with quite a lot of opened IE windows. I use Chrome as my main browser so I don’t mind killing all the IE windows to cleanup. To make it easy I use batch file with this command:

taskkill /F /IM iexplore.exe

1	taskkill /F /IM iexplore.exe

Starting Vim (gVim) from IntelliJ

Posted on 2013/09/13 by devmake

Ever wanted to use Vim editing features while inside IntelliJ IDEA? Here is how to do it… You can even jump to the very same line you are on in IntelliJ.

Go to Settings > External Tools, add a new tool and use something similar:

Program: c:\Program Files (x86)\Vim\vim71\gvim.exe Parameters: "+call cursor($LineNumber$,$ColumnNumber$)" "$FilePath$" Working directory: $FileDir$

Update: IdeaVim – Vim commands right in the IDE

Additionally I finally tried the IdeaVim plugin for IntelliJ and my experience so far is pretty good. The need to start gVim externally almost disappeared.

Update: Open file in IntelliJ from gVim (Windows)

Save file + Open current file on the same line in IntelliJ + Close file in VIM

map! <F3> <Esc>:update<CR>:silent exe "!openIntelliJ.bat c: --line " . line(".") . " %:p"<CR>:q<CR>

:map! command creates a key map that works in insert and command-line mode.
:update is similar to ":w" or ":write", but only writes when the buffer has been modified.
silent prevents Hit enter cmd window.
line(".") returns current line number (dot is for the current)
%:p returns full file path of the current file
IntelliJ commmand line uses following syntax: [IntelliJ Path] [path1 = path to the project that contains the desired file] --line[number] [path to the file to be opened]

Here is my openIntelliJ.bat – one of the advantages is that I have just one place to change when I upgrade to a newer version (giving the exe to path variable would an option too):

start "" "c:\Program Files (x86)\JetBrains\IntelliJ IDEA 12.1.6\bin\idea.exe" %1 %2 %3 %4

The second attribute for Windows “start” command is title, I don’t need it, so I supply empty string.

References:

Adhoc logging in Eclipse

Posted on 2013/07/12 by devmake

Background and motivation

Very often it is more useful to log variables to console or file (using Log4J for example) instead of using breakpoints and manually step over. Especially when the execution goes through the interesting line multiple times debugging can be quite annoying.

When we are dealing with our code, it is pretty easy to add a log statement to the specific part. When we are dealing with 3rd party code we don’t have such options. In such a case we can achieve this using AOP (e.g. AspectJ or Spring AOP), however sometimes it is just too heavy solution when we need to do this one time only to find a small bug or so.

One day I came accross an interesting article 5 Tips for Debugging Java Code in Eclipse written by Abdullah Cetin CAVDAR on September 13, 2008. Fredrik Attebrant made an interesting comment that helped me to achieve what I all the time wanted:

“Trace points” can to some extent be done by entering code into the “condition” of a conditional breakpoint.

First do some printing, then make sure to return false if you want the execution to continue.

Example:
System.out.println(” foo has size: ” foo.getSize());
return false;

How to use adhoc logging in Eclipse

So here we go… we will use conditional breakpoints in Eclipse to enable us to log important stuff.

Create a breakpoint on the line you are interested in. Right click that breakpoint and select Breakpoint Properties…. Check “Enable Condition” checkbox and input your code into the box below. The breakpoint icon will show a question mark on that line meaning that it is a conditional breakpoint now.

The trick here is to do the output and then return false so that execution is not suspended and you do not have to interact with the debugger as it is exactly what we want to avoid (see the option below the text box: Suspend when – condition is true).

To test it, we obviously have to run the program using Debug instead of Run because we need to enable breakpoints. The output should be similar to following:

Started LOG - 0 LOG - 1 LOG - 2 LOG - 3 LOG - 4 LOG - 5 LOG - 6 LOG - 7 LOG - 8 LOG - 9 Finished

There is more to try…

And going further we can even implement conditions (hence conditional breakpoint), so that we would log only under specific circumstances.

Tip of the day

Posted on 2012/02/26 by devmake

The Ultimate Productivity Blog – http://productiveblog.tumblr.com/

Devmake

Tech blog about random things that I find interesting