Is there a way to set the default highlighting level to Syntax instead of Inspection?

I am finding that inspection level highlighting is too slow fr the size of my projects/speed of my work PC (Core i5, 3.25GB) and would like to be able to set the default highlighting level to simply syntax.

Is this possible?
35 comments
I'll take the lack of input as a 'no'.
2
If you go to Settings|Inspections you can turn off any inspections that you don't require - I think that is what you are meaning by the level of highlighting.

For example, if you are doing a project that isn't Django based, you might as well turn off all of those - no point in having the test running no matter how briefly - similarly for CoffeeScript, Google App Engine and so on.

Just select the ones that you are actually going to possibly require and things should pick up somewhat for you.
-3
No, and we have no plans to provide this possibility. In our point, turning down the default highlighting level effectively cripples PyCharm, and if the only way PyCharm works for you is in a crippled state, then you shouldn't try to suffer through this and should use another tool instead. (And before you do that, it would be nice if you could send us a CPU snapshot as described in http://devnet.jetbrains.com/docs/DOC-1212 so that we could fix the performance issue.)
-15
That's a very good point Dmitry, shutting down the inspectors does lead to crippling the environment - really negating the whole point of using PyCharm in the first place.

I use RubyMine and PhpStorm besides PyCharm, and the whole ethos of using the inspectors is what makes these tools so good to work with in the first place: the suggestion I made in my other message was ill conceived only taking into consideration a way to achieve the requested aim, rather than taking into consideration what the outcome would be.

Thank you for taking time to give your input.

Geoff
-3
I don't think adjusting the highlighting level from Inspection to Syntax takes away so much that I should be using another program. Just because the syntax highlighted becomes less helpful doesn't mean that the UI layout breaks, all of the plugins cease to exist, and how I like to work is gone. I can like the program without requiring the hand-holding part of it.

Just to clarify I am not talking about specific inspections. The adjustment I am constantly making, per-file, is by clicking the icon in the bottom-right corner for the application and dragging the slider to make the adjustment (speaking of which, it's odd that the slider MUST be dragged and a spot along it cannot be clicked).

The symptoms I often experience if I do not adjust the highlighting level are:
Very long inspection times (the eyeball icon at the top of the scrollbar area)
Very long pauses when PyCharm regains focus after being away
Very long pauses when right clicking within code
Very long pauses when clicking any level of the directory structure (the navigation bar under the toolbar)
Lagged typing (letters showing up well after I typed them)
and more

I think some of this has gotten better after the last update but I am still hesitant to go back though my files and set them to Inspection-level highlighting.

I've had the same issue across two machines. I've taken steps to try and improve things myself, such as turning off antivirus/antimalware scanners. Defragging. Turning off Windows Search Indexing. Etc. I've also disabled unused plugins in PyCharm, I've only got the needed directories in my project scope.

Personally it sounds more like a memory issue than CPU, however I always seem to have 20-30% of my memory available according to taskmgr.

Also I should mention that 99% of my work is actually JavaScript & CSS. I rarely open Python files, however, my projects are all python (Turbogears) backends.
4
I will take a look at the link you've provided.
0
I often have to lower the highlighting level to "Syntax". Because of this issue http://youtrack.jetbrains.com/issue/PY-9510 there are soooo many yellow highlights in the right-hand bar that it's impossible to use. I hope this is fixed soon, as otherwise PyCharm is an excellent tool and I don't want to switch!
0
I end up setting the level to Syntax manually for multiple files. I respect the devs having high principles and standards, but it is not right to force the customers to either stick to the high default notifications level, or disable pycharm at all. It should not be a modal decision, not the one forced upon customers by the devs anyway.
2

that's pretty awful that you guys won't even consider the option. not all of us have the luxury of working in a codebase that's so beautiful and perfect it doesn't make the IDE choke. 

1

I switched to Visual Studio Code and haven't looked back. Fantastic alternative.

1

Pretty sad that this capability is not provided especially given that 99% of the stuff the "inspections" show me as error/warning or whatever is pretty useless. It literally complains about everything, includding invalid imports (which is incorrect because the imports work fine), adding trailing spaces, not adding trailing spaces, it complains about comments being too long...

 

Seriously, PyCharm is a great editor but the inspections are excessive and most of the time simply annoying. We have 3 developers in the team, and we all have the inspections turned off because they have such a fine-grain level of complaining that they only reduce productivity.

3

Came here googling about this issue for IDEA. Bit of a shame to see Jetbrains adopting Apple's "we know better than you" attitude forcing their preferences on users.

I want to work in the way that is most comfortable to me and my productivity, without a rainbow of colors and irrelevant highlights annoying me everywhere. Without having to manually turn down the inspector level on every file I open. It's really not that much to ask for. 

Mind you, this is still kinda achievable by just deleting all the inspectors, so in the end we're still at the same result which was just more annoying to achieve. 

4

"No, and we have no plans to provide this possibility. In our point, turning down the default highlighting level effectively cripples PyCharm, and if the only way PyCharm works for you is in a crippled state, then you shouldn't try to suffer through this and should use another tool instead."

I do not support this attitude, in general.  Specifically, unless you can't write code in the editor, the software isn't crippled.  Frankly, the inspections are often far more crippling than any lack of inspections would ever be.  Any delay in code editor input is far worse to me than the benefit of having real-time inspections.  If I want analysis to be run on my code, I will do so when I see fit.

If I needed a life jacket, I wouldn't have gotten on board in the first place.

 

 

 

3

I would love to have this feature. Your reasoning for not allowing this is also not internally consistent. If you allow users to change the highlighting level for an individual file, then you should allow users to set the default highlighting level as well. I am personally working with a legacy codebase that is over a decade old, and probably 90% of the lines get highlighted by default. So instead of making syntax-level highlighting the default (which I should be able to do), I instead have to just turn off all inspections. I shouldn't have to do that.

2

it's not. that stackoverflow question is turning off inspections, not setting a default highlighting level.

1

The reply of @Dmitry is not acceptable in my opinion. If this option is not possible (although I don't see why), please explain why instead of basically saying "use other tool if you aren't happy"!

2

By default, all enabled code inspections apply to all project files. If necessary, you can configure each code inspection (enable/disable, change its severity level and options) individually for different scopes. Such configurations, like any other inspection settings, are saved and applied as part of a specific profile.

There may be complicated cases when an inspection has different configurations associated with different scopes. When such inspection is executed in a file belonging to some or all of these scopes, the settings of the highest priority scope-specific configuration are applied. The priorities are defined by the relative position of the inspection's scope-specific configuration in inspection settings: the uppermost configuration has the highest priority. The Everywhere else configuration always has the lowest priority.

For more information and procedural descriptions, see Configuring Inspection for Different Scopes.

1

Very sad response from the jetbrains dev team.

What I have to end up doing .. IN EVERY PAGE IN THE PROJECT...  is clicking the icon that looks like a microphone (in the bottom right corner of the ui) and adjusting both the PHP and HTML sliders:

4

for some strange reason this same popup randomly shows these two sliders flipped in position, which makes adjusting them quickly that much slower.



 
 

2

Super dumb!

Do I have to disable all inspections when I could be given the option to choose the default highlighting level?

The UI itself is terrible for choosing the level for individual file:

  • The icons used are a bad choice. It looks like a microphone to some, but it's actually a guy wearing a tall hat. He smiles at None, looks to the right at Syntax and frowns at Inspections. I have no idea what those are supposed to mean. Happy, Distracted and Unhappy?
  • --- Seriously, which moron designed those icons? Are you trying to be cute? Icons should be simple. None: O with / across. Syntax: </> (the most common syntax icon). Inspection: Magnifying glass or Eye (which is ironically used in the sidebar).

  • The slider cannot be clicked to move it to different positions. It has to be dragged. This is a non-standard behavior. Standard sliders can be clicked to nudge it to where it is clicked (either instantly or in steps).

  • If there are two or more sliders, they don't appear in a consistent order. This gives user the inability to predict the slider position and quickly move the correct slider. The user always has to stop and look.

  • There is no alternative to the big slider menu. Couldn't I right-click to summon the context menu and choose my desired highlighting level from a small and simple menu that just lists the options? Why force me to move my mouse around dragging a slider?

And finally the crux of it all: NO SETTING TO CHOOSE DEFAULT HIGHLIGHTING LEVEL either for the Project or for the IDE.

Well I'm pretty Unhappy now, just like the default icon (frowning guy with the tall hat).

5

Workaround for IntelliJ

Thanks to Rogerdpack2 to pointing us to https://stackoverflow.com/a/44758847/1134080

  1. Open the Settings
  2. Go to Editor - Color Scheme - General
  3. Select Errors and Warnings - Weak Warning
  4. Uncheck the Error stripe mark
  5. Hit Apply and close the settings window

You can also do this for the normal Warning if you still receive too many highlights for your needs.

For me, I also unchecked it for normal Warning, TODO and Typo as well.

0

ADTC - Unless this somehow disables the analysis process, it isn't solving the core problem.  There is demand for a global setting, and the only counter-argument presented is "JetBrains is smarter than you."  

3

I would love to have this feature.

1

It's been almost 5 years, and plenty of people still want this option.  Maybe it is time to allow the users to decide best how to use.

1

ya.. they don't take fixes serious

0

This issue puzzles me I have struggled months lowering the level on every file and decided to change the default setting. And no default setting, come on guys this is not serious instant phpStormCharm lost. Please, reconsider your decision.

0

I'm surprised and somewhat disappointed to see Jetbrains taking this ivory tower stance.

Codebases are not always as clean as we'd like them to be.

The least they could do is allow the weird man in the hat button to change the inspection level at a directory level, rather than force busy developers to adjust the settings in every single file, one at a time.\

I'm doing that for twenty files right now, and let me tell you, it's not a 'pleasure' at all.

 

0

There is related issue on YouTrack: https://youtrack.jetbrains.com/issue/IDEA-107752. Feel free to add your suggestions in comments.

0

It is often hard to figure out where the scroll bar handle is due to overcrowded highlight marks along the bar. Also the inspection highlights make it difficult to spot occurrences of, let's say a selected symbol. After all as the highlight setting can be adjusted on a per-file basis, it is a reasonable expectation to find a project level config for that too.

I am a newcomer to jetbrains from eclipse world after having been there for nearly 12 years now. It is surprising to discover that such an obviously useful feature request is hanging around here without any luck since 2013!

3

Please sign in to leave a comment.