eclipse ctrl+k equivalent shortcut in IntelliJ

Question

In Eclipse, if the cursor is over a word and you press Ctrl+K you will jump to the next occurrence of that word in the file.

Is there a si

Answer 1

Keymap : Mac OS X 10.5+

• To start / add to your discrete multiple selection : CTRL+G
• To skip the current selection and move to the next : CMD+G

Refer: Does IntelliJ have a `Ctrl` + `K`,`Ctrl` + `D` Sublime equivalent? How do I skip a match when using Alt+J for multiple selections in Android Studio?

Answer 2

I think Android Studio/IntelliJ doesn't play that well, for me, I changed Android Studio Keymap to Eclipse as I used to (My collection tips) and to use Ctrl+K, I press search the string first:

• Select the text we want to search
• Press Ctrl+F, Enter
• Then can use: Ctrl+K in any file we are on

That's what I'm doing, hope can help someone with that.

Answer 3

You can do it using macros:

• Edit -> Macros -> Start Macro Recording
• Edit -> Find -> Find Word at Caret
• Edit -> Find -> Find Next/ Move to Next Occurrence
• Edit -> Macros -> Stop Macro Recording
• Give some name for the macro, e.g. "simulate Eclipse Ctrl+K"
• File -> Settings -> Keymap -> Find the macro "simulate eclipse Ctrl+K" -> bind hotkey Ctrl+K

The same can be done for the Ctrl+Shift+K (use Find Previous/ Move to Previous Occurrence).

Answer 4

You need to first do Ctrl+F on the selected word, now this gets cached then you can use the Ctrl+L and ctrl+shitf+L for going down and up respectively. This is already present. its just that instead of ctrl+K you got use ctrl+L. small change same effect

Answer 5

In IntelliJ, if the cursor is over a word and you press Command+G you will jump to the next occurrence of that word in the file. Similarly, you press Command+Shift+G you will jump to the previous occurrence of that word in the file

Answer 6

There are 2 options like below in : Settings -> Keymap -> Main menu -> Find

• Find Next / Move to Next Occurrence
• Find Previous/ Move to Previous Occurrence

For me, this didn't work at the start because GIT push shortcut was using the same keys (Ctrl + K & Ctrl + Shift + K). All is good after changing the conflicting GIT shortcuts.