Intellij indexing entire filesystem - how to stop it? - intellij-idea

How to stop Intellij from indexing the entire filesystem and not just the project? did i screw up a setting somewhere somehow? where is it and how to fix it?

Related

Intellij IDEA search functionality always stops working

The find in path search works on newly cloned/downloaded repos. But I notice after a few days, all search functionality in the IDE just stops working. Searching for anything string turns up 0 results in project, module, directory paths. Anyone else experience this? It's infinitely infuriating T.T
OS: Mac
Version: Intellij IDEA Ultimate 2020
Settings: only default
Please, try to invalidate caches via File | Invalidate Caches / Restart option.
It's a known issue IDEA-266391 and you can update IntelliJ IDEA to the 2021.1.1 version with the fix.
So it turns out this is happening whenever I change branches. So your suggested soln above works well. thanks!

Why do so many files in IntelliJ have the nginx icon?

I noticed that many of my files had their icons changed and IntelliJ's auto-formatting is broken for them. I don't know what I did before it happened because I didn't notice it right away.
The "File Types" config seems fine to me:
If I rename one the affected files, the icon changes back to the correct one but since I don't want to rename all of those files I wonder if someone here has an idea how to fix this in a better way.
I'm using IntelliJIdea 2020.1

Intellij 2018.2 stops working and exits on MacOs. What might be a problem?

As an daily IntelliJ user you usually concentrate on the projects you are working on and IntelliJ is just a tool. You are not willing to dig into tool's problem itself. But this is what is forced on you by default after IntelliJ installation on MacOS and opening relatively big project(most of the projects nowadays are huge and have thousands of files and use numbers of IntelliJ 3rd party plugins).
Here is a minimal list of actions. IntelliJ must have set MORE RAM to be used by default.
Read: https://intellij-support.jetbrains.com/hc/en-us/articles/207241085-Locating-IDE-log-files .
From IntelliJ open Help / Show log in Finder and open idea.log file with Console.app; In Console.app press "Reload" and "Now" buttons to track "live" what IntelliJ is doing.
If in logs of IntelliJ you find that some of the plugins exit with fatal error, you just uninstall those plugins. For me the one that failed to the moment of this answer was "BashSupport" as example.
Start Terminal.app ; Run command: open -a TextEdit /Applications/IntelliJ\ IDEA.app/Contents/bin/idea.vmoptions ; Change options in idea.vmoptions file to:
-Xms1024m
-Xmx2048m ; Read https://www.jetbrains.com/help/idea/tuning-the-ide.html to see how you can tune IntelliJ for your project. This step is handy when your IntelliJ app doesn't start at all and you want to change properties in a global way.
From IntelliJ open Help / Edit Custom Properties.... Here you can set same properties that will override global and will work only for current OS user.
Also there is also a possibility of underlying OS to do it voodoo magic so the IntelliJ won't work as it should like here - https://intellij-support.jetbrains.com/hc/en-us/community/posts/360000398280-IDEA-Ultimate-2018-2-Unable-to-save-settings-Unable-to-create-file-Windows-10
Make sure your project build output for *.class files is set. Read: https://intellij-support.jetbrains.com/hc/en-us/community/posts/360000000584-Build-does-nothing . In my case when IntelliJ started project build it terminated without warnings shortly after.
Finally in my case none of 6 steps above solved the issue so I found this read: https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000532044-IntelliJ-cannot-build-projects . Basically try reinstall IntelliJ from original distribution again.
I know that you must read https://www.jetbrains.com/help/idea every time you install a new version of IntelliJ, but why not to add some consistency into configuration process of the main java process that runs IntelliJ itself? You can ask how much ram to use during installation of IntelliJ and explain why it is so. Then Help digging won't be necessary in the first place for devs who fed up with changing those default settings that will be always more than 700MB. I think for most devs out there it is at least 10x of that. I bet what makes most devs mad about this is not the fact that you need to do some options changing, but where those options are depending on OS plus the fact that you simply forget why IntelliJ app just exits while you are doing a debugging of your own app. I bet this problem makes us mad since first java based IDEs appeared. User-friendly is the key here and explicit reminders within the app itself would help.

How to ignore certain directories while synchronizing in IntelliJ IDEA

I use samba to mount remote directory locally to use IntelliJ IDEA, but my project contains many large files, and they do not need to be used by IntelliJ IDEA. Luckily, the files are put under several directories, so maybe I can ignore these directories to speed up synchronizing process. I failed to find any setting about this features. It is such a pain to wait several minutes before actually do anything. Does IntelliJ IDEA support such feature? How can I enable it?
You can try to Mark Directory as Excluded. Even though below link is for CLion, I believe, it works in a similar way in Intellij as well.
https://blog.jetbrains.com/clion/2015/12/mark-dir-as/

IntelliJ and Symlink cycles

My build step involves creating symlinks to javascript folder.
It seems that everytime I reopen the project in IntelliJ it always fails to load the project if I had not deleted the symlinks before closing it. Discovered this after wasting numerous hours! Is there a way to configure IntelliJ to not follow symlinks or maybe ignore certain folders?
BTW. Why symlinks? So that while I am testing/developing I can make source code changes and that reflected right away. During deployment instead of symlinking I can copy files (and perform minification + optimization).
So, the situation was, we were inside an environment where npm was not available. And what I needed was something akin to npm link. Taking up Roman's advice, I decided to spend sometime and ensure no cycles exist.
Transitive dependencies made it a bit of work to detect cycles.