IntelliJ - Debugging set next statement? - intellij-idea

How can I step back to a previous line when I'm debugging in IntelliJ?
I don't see anything in the debug menu or commands to do this.

There's no backward debugging support in IDEA currently. Nevertheless (for Java) there is Drop Frame action and button on the debugger toolbar. It lets you go one frame up in the stack and re-enter the current method.

The Chronon plugin, which is available for free with IntelliJ IDEA 13, can do this for you. It has limitations, though; chiefly, if your application runs outside of the IDE itself (like a Tomcat or Jetty server), the free version won't be usable with your setup.

Related

Tooltip doesn't let me type text when it is appeared. IDEA's editor

I am working with Itellij IDEA (2017.2.4). I am not sure whether the reason is new version of IDEA, but I started to face it after new version installed.
When I type some code in editor and Tooltip is shown (it can be inspection or just parameters of method shown ect.) I cannot type new symbols until pressing ESCAPE button, it is not useful for me. Before updating the IDEA there was behavior when user types new code, tooltip is hidden without ESCAPE pressing. It was made hidden by any key pressed.
Actually maybe I just change some setting property unconsciously, if yes - what is the property needed to be restored to default?
How to make it hidden not by ESCAPE but by any button?
In next image I pictured the moment when only ESCAPE key can be pressed.
I'm not able to reproduce the issue, even when I use v2017.2.4 on windows. The behavior should be that you can still type even when the tooltip is present:
I can't think of anything in terms of settings that could cause this issue. If it's just the "parameter info" tooltip that is causing the issue, you can disable it (or just increase the delay time) from automatically popping up via the setting: Settings > Editor > Code Completion > "Parameter Info" > "Autopopup" You can then manually open it via the Parameter Info Action via Ctrl+P / ⌘P. The setting #Maciej-Białorucki mentioned will effect the time before other tooltips open. Setting to a high value might help if other tooltips are causing issues.
Personally, I find the auto popup useful. To troubleshoot why this is causing issues, I'd recommend trying the following:
Upgrade to v 2017.2.6 which was released yesterday. While I personally can't reproduce it, and I'm not seeing anything about it in the 2017.2.5 Release Notes nor the 2017.2.6 Release Notes, it can't hurt to try and upgrade.
Disable all third party plugins and restart IDEA. See if the issue persists. In my 14 years of using IDEA and helping people with it on the forums, I've seen 3rd party plugins having bugs that cause other parts of IDEA to misbehave. Since you recently upgraded, it's possible a 3rd party plugin is having a compatibility issue with the new version. If the disabling them solves it, use a binary search to as you re-enable the plugins to track down the culprit and then report the bug to the plugin's developer.
See if it happens in other projects. If not there may be something wrong with the project's configuration. (A long shot. But worth checking out)
As another long shot, you can try invalidating the caches and then restarting IDEA via File > Invalidate Caches / Restart... I have on occasion over the years seen a corrupted index file or cache cause strange behavior.
If none of the above work, I suggest opening a bug report with JetBrains at: https://youtrack.jetbrains.com
Check Tooltip initial delay(ms) option under Appearance in Idea settings.
As I divined there was a property in settings that influences to the behavior described in a question. So to continue writing code without pressing ESCAPE key you must uncheck the following property:
Menu page Settings -> Appearance & Behavior -> System Settings
Checkbox Accessibility -> Support screen readers (requires start)
(for more details see the link)

Change default tool window behaviour in IntelliJ IDEA 2016

Every time I open a new project in IntelliJ IDEA, the first time I open a particular tool window, for example 'Maven Projects', it appears in 'pinned' mode and remains visible until either I close it, or I go to the view settings for the window (the little cog) and deselect "Pinned Mode". I don't want any of my tool windows to be pinned so this gets a little annoying.
Do you know of a way to change the default behaviour of new project / tool windows?
As far as IJ 2016.2 I don't know about a dedicated setting for this. However I used an approach which allows you to define a default layout for all projects. Although the window-pinning works, which is what this question is about, some may not be persisted, such as Group Modules setting in the maven tool-window.
Nonetheless, to configure the pinning, you need to do 2 simple things, which you can also see in the GIF below:
1) Manually go and unpin all desired windows
2) Open the Windows menu and select Store current layout as default
P.S. If you'll be using tool-windows that you've never opened before, or install new plugins which add their own tool-windows, just follow these steps again.

Can't type in IntelliJ

I'm using IntelliJ IDEA on my Mac to work on a project, and I keep on coming across an issue where I can't type. Occasionally when I switch to another application and then switch back to IntelliJ I can't type anything, and the cursor doesn't appear on text when I click on things. Does anyone know what causes this? After 1-2 minutes it goes back to normal, but it's started happening more frequently and it's pretty frustrating to not be able to type and have no way to fix it.
This is the version of IntelliJ I'm using:
IntelliJ IDEA 2016.1.3
Build #IC-145.1617, built on June 3, 2016
JRE: 1.8.0_76-release-b198 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Turn off Vim Emulator from Tools in the IntelliJ, like this picture:
I am encountering this issue aswell, ...
MAC os Mojave 10.14.2, Inteliij Community 2018.3.5
Aside from restarting / clearing caches, I found that cmd + leftShift + F still opens the search window, and all my keystrokes appeared in the searchbox!
After the searchshortcut, I was able to close the searchbox and work again!
The answer here helped me https://intellij-support.jetbrains.com/hc/en-us/community/posts/206152119-Can-t-type-in-editor-window
Quoting the author of the answer:
I had the same problem. It goes away after I click the icon at top of
the scroll bar. it happens frequently on windows 7/10, and
occasionally on mac. my colleagues said they have experienced it too
Have the same issue occasionally, can't type in any Intellij windows. My temporary/quick fix, is to:
Close any terminal windows in intellij
Use cmd+shift+f to pull up the search window.
Seems to fix it, for a while.
Closed IDEA, all IDEA projects! Even though in other IDEA windows I could type.
Removed .idea folder in the project I could not edit.
Restarted IDEA.
Then I was able to type!
Maybe you entered Vim emulator as said. Maybe only by mistake :).
Control-V is a frequently used shortcut. And Control-Alt_V is the shortcut to enable Vim mode so you can see the problem...
How to know in five seconds: type a ":" (colon) and if the cursor jump to end of the screen, that is vim. If so enter q to quit and then Control-Alt-V (on windows) to go back to IDEA standard mode.
vi is a powerful text editor since ever. But only if you pretend and know how to use it... There is even a warning on the IDEA install saying like "do not install unless you are familiar with Vim" in yellow bold text, iirc.
[Follows historic data, that you may find boring off-topic or interesting]
Today's editors opens the code in edit mode right away so you can start typing over existing code. Vim by the other hand opens the code in, let us say, browsing mode: there is a set of navigation keys to browse the code. Everything you type is supposed to be a command. When you want to edit you enter INSERT mode and then you can type new text. Only then.
Just for more historic data: vi navigation mode is great for studying code you do not know, using IDEA, since it does not change the text unless you tell it to, and some vi commands are clever.
One example:
"/" (forward slash) is one search command, and "z" is a smart scroll command so that:
/setCellFactory will search for the next match of "setCellFactory" and put the cursor there
Then if you type "z" the code will be positioned so that line is the first on screen. And if you type "." the line will be at the middle. And if you type "-" that line will be at the last position at the screen. And you can use these commands again and again. And new slash will go for the next match, like F3
This "z" thing is a feature I miss in Visual Studio, IDEA, Eclipse, Word, WordPad: these commands to scroll text AROUND a pattern... /pattern, z, z., z-. The alternative is the mouse wheel...
I am used to vi since the 80's and is the editor I still use today on Linux terminals so when this happened to me on IDEA I was lucky to remember and suspect of that on the first time.
Sorry if these details are boring
Ensure you haven't unintentionally enabled vim emulation. Go to IntelliJ Idea -> Preferences and select Plugins. Scroll down and look for the vim emulation plugin and if it's checked, then either uncheck it or uninstall it completely.
Ran into same issue with intelliJ 2017.1.2, but no VIM Plugin. However, I had just created an empty project with some .groovy files. I could edit the files in the groovy project, but not java projects.
Only way I could fix java projects, was blow-away workspace.xml files in each, then I could edit again. However, had to re-create tomcat configs, breakpoints, other IDE settings. etc.
I had a problem with entering characters when working with .story files. When I tried to type in any character, it appeared for a short while and immediately disappeared. The cause of the problem was jbehave plugin I was using. After uninstalling it and restarting IntelliJ everything was fine.
It seems to be because another window has the cursor and is not giving it back.
Check any open floated windows, click on them & then click back to your intellij instance
alternatively, if you have multiple intellij instances open the cursor could be there...
Go to the most recently opened IntelliJ instance
Check if the cursor has become stuck in that project's terminal window, or another window
no? check all other open IntelliJ instances
For me it happened because of vim
Om Mac, I solved it by navigating to File → Reload All from Disk.
Keyboard shortcut: ⌥ ⌘ Y
IntelliJ IDEA 2020.1.4
Try disabling plugins one at a time. It was the "BashSupport Pro" plugin that caused it for me. Disabled it and I could type again right away.
I read other comments saying some other plugins caused the issue as well.

Missing "messages" window after compilation in IntelliJ

I'm using IntelliJ IDEA 12. When I run "make project", "debug" or "run" task it does some compiling, shows little bubble that there are warnings, shows grayed-out tool window "message" and after few seconds it hides the nameplate of messages window.
Why is compile log missing? What to do to fix this? I'd like to see (in IDE) what causes those warnings...
PS: I'm not sure, but it might started doing this when I started using Scala (it's now a mixed Scala-Java project).
If you've previously selected "Hide Warnings" then the Messages window is unavailable if there are no compilation errors. It is not even possible to show the empty window using View->Tool Windows-> Message or Alt-0.
Solution:
introduce a compilation error
build, the Messages window should reappear to show your error (or at least be accessible via the View menu)
go to the Messages window and deselect Hide Warnings
fix the compilation error
Rebuild Project and all your warnings will be visible
(I had the same symptoms on 13.0.2 and this worked for me)
For me, it pops up on "Rebuild Project". Maybe that helps.
The window should be there any time IDEA compiles the code. (If there is a not a code change, and you rerun something there is no compiling done and the message window will not show). It is accessible (by default) via Alt+0 (Zero, not the letter 'Oh') or via View > Tools Windows > Messages
You may have a combination of some tool window settings causing this.
If all the tool window buttons are hidden, the messages tool window will be as well. You can toggle this setting via View > Tool Button or the icon in the very bottom left corner of the IDE. To temporarily show the buttons when hidden, hit the Alt twice, holding it down on the second hit.
If the messages tool window is not set to "Docked Mode" and "Pinned Mode" it will close after the compile.
If the above is not the issue, make sure you are using the latest version of IntelliJ IDEA, v12.1.6, and the latest version of the scala plug-in, v0.22.302 (Go to Settings > [IDE Settings] > Plugins and look for the scala plug-in). Those versions work as expected for me.
Looks like u do not have any errors and warnings! In this case in Idea "Messages" tool window auto disappears. I hade the same issue and passes half an hour to understand the reason!

Submit Eclipse Project on Perforce

I have a noob Perforce question. I got my perforce plug-in on Eclipse working(for both Java and C).
I have no problems "opening" my perforce stored projects on Eclipse.
Scenario 1:
Whenever I want to change code, I open the project on Eclipse and right-click on it and go to "team" and check out, make changes and then submit. Works fine. But even after that I see a tick mark(indicating check-out) on my perforce screen.
Scenario 2:
I just open perforce code as Eclipse project and make changes(If read only, it prompts and asks if i have to allow write and I say yes). I make changes and save. It doesnt ask for submit. Also if I now open the code on Perforce screen, I already see the new changes made.
Scenario 3:
Just on a Perforce screen, if I check a file out and don't make any changes, I obviously dont want to submit as there are no changes. In this case, how can i "disable" check-out so that my fellow programmers dont think i'm working on it??
Scenario3:
So here are 2 ways i consider a good usage of the plugin:
Use Revert Unchanged Files:
Before you begin development of a feature, checkout the entire tree/branch that your changes will be concentrated around in future. You can do this by right-click the relevant package in package explorer. Once you want to submit, Project->Right-click->Team->Revert Unchanged Files. Now, you can submit your changelist.
This approach stands very useful if you know you will be editing a lot of files or replacing files.
Ofcourse, others can see that you have checked out the files.
Enable Auto checkout:
Incase you are going to make few changes, you should enable autocheckout. This will checkout the file when you begin to make edits. Eclipse->Preferences->Team->Perforce->Enable support for workbench edit..
detailed explainations here. Its a good idea to have this enabled always as it checks out on demand.
However, this does not monitor the filesystem so and code/libs you replace outside of eclipse are not checked out.
For Scenario 3, you can change a workspace option to prevent submitting unchanged files:
SubmitOptions: reverttunchanged
If you have a file checked out (open for edit), others will be able to see that. I guess I'm not clear on why you check a file out if you don't intend to modify it?
If you are going to setup this way and are also using the desktop client, I recommend the following steps in the desktop client:
1.) Open your desktop Perforce client
2.) Click “Connection” on the global menu
3.) Select “Edit Current Workspace…”
4.) Under the “Advanced” tab select “allwrite”
5.) Click Apply, then OK