IntelliJ: How can I "kick" the error highlighting process to get it unstuck? - intellij-idea

I'm working on a create-react-app codebase with Typescript enabled.
I find that IDEA real-time syntax analysis of my code often gets "stuck".
I make a mistake, IDEA shows the little red squiggles almost immediately, then I fix the errors but sometimes the red squiggles don't always go away.
For example:
There's nothing wrong with the above code any more, but IDEA still shows the red squiggles, both in the code and the project tool window / changelist window.
I've found that I can "un-stick" the code analysis by killing any/all the node.exe sub-process that IDEA has. Presumably one of those sub-process is "stuck" and when I kill the process, IDEA launches a new one and the syntax error highlighting will disappear.
Obviously, I'd prefer that the code analysis not get stuck at all, but failing that is there a way I can "un-stick" the code analysis from within the IDE?
I'm looking for something faster than re-starting IDEA (or clearing caches, etc.)
Using IntelliJ IDEA 2020.3 (Ultimate edition) on Windows.
package.json configuration and the rest of the code can be found here: https://github.com/kopi-cloud/cabbage/tree/main/app

As per comment from Lena, restarting the Typescript language service will fix issues with stale highlighting errors.
The Typescript status bar widget is usually found at the bottom right of the editor:
Tested with IDEA 2021.1.2

Related

My classes in project randomly become invisible to other classes in intellij

In my IntelliJ editor, I am facing this trouble that randomly some files becomes invisible to other files using them.
I have tried refreshing the workspace and even rebuilding the project but error won't go away even though the build never complains, the problem would suddenly disappear for a file and reappear for others.
When class is available it should not give red squiggly lines in the editor as it hampers in other code editing tasks.
I found the solution to this problem it's simple
goto File | then select invalidate cache and restart option, it resolved the issue, answering.

How can I force intellij to check all files?

When I'm using intellij sometimes I do very large refactors that the IDE can't help with. This often breaks a lot of files, but since I'm using either Typescript or Java it's relatively easy to find the problems.
My issue is that I can't seem to get Intellij to check those files unless I open them specifically.
The kind of checking I'm talking about isn't a specific inspection, it's just like the normal compilation problems.
So for example, I have a typescript project and I modified some stuff. When I open some of my React components intellij waits a second, and then highlights parts of it in red. I can go to those parts and see what the issue is.
I've tried forcing the inspector to run, and I've tried building the project, but neither one gives me the red squiggly love I need :^(
It feels like the project->build should force intellij to highlight all this stuff, but it seems to have no effect.

Codewarrior 10.5 broken links from problems window to errors in code

Typically when I compile a project I am working on in Codewarrior, the Problems window displays the errors and warnings it finds. From there, I am able to click on the errors and I will be linked to the location of the error in the code. In the current project I am working on, the errors are displayed in the problems window, but they do not link to the error. It shows the correct file and path, but the hyperlink to the location in the code is broken. In the console window, I can use the Next/Previous error buttons to navigate to error, but I can't do this from the Problems window - which I find easier to read. I know that this error is limited to this project, because I have opened other projects since this started happening and do not experience this problem in those projects. When I started this project, I copied an existing Codewarrior 10.5 project that does not have this issue and began changing names and editing. I have a suspicion that I might have missed something during this conversion process, but I am running out of places to look.
I'm not sure the exact reason for this error, but I did correct it by deleting the folders in the workspace folder and re-importing the project.

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.

How to see live list of syntax errors in WebStorm 7 (or IntelliJ)?

While editing a JavaScript file, the IDE shows highlights on the lines that have problems and displays the lightbulb when you're on one of those lines.
How can I see a live list of all problems found in the current file (e.g. syntax errors)?
The only way I found so far was to manually run inspection and check the inspection window. That's quite cumbersome. Even the "Problems" section of the Project window updates itself automatically as soon as I change the code (even without saving) - but it doesn't display the actual errors (only which files have errors).
Apparently the IDE knows what errors exist in the file - I just can't find a way to see all of them in a list.
In every other IDE I know, it is a built-in, enabled-by-default, feature: eclipse, visual studio, brackets, etc.
Apparently this is an open issue on the IntelliJ family of products. Please upvote that issue if you feel it is missing as well!