Mr. Inspector -- What's "Power Save Mode", and where's my "Pause on edit only" button?

I see there is a new "Power Save Mode" for Mr. Inspector.  Not sure what that does, but that reminds me --- where is my "Pause on edit only" button aka  IDEA-14683 ?

IDEA pauses the syntax/inspections parse on key presses when the file  is not even being modified. Clicking on the editor pane with your mouse  also pauses the syntax/inspection parse. (However, just moving your  mouse over the editor panel (no clicking) does not pause the parse.)

When  I am browsing files, e.g. stepping through the usages in a file, or  just studying some code, what happens is the syntax/inspections parse is  getting paused if I press any key. After the auto-reparse delay, it  will restart the syntax/inspections parse, but if you type another key,  it pauses again.  Note that I am not editing the file(s), just  navigating it with the keyboard, my cpu is at ~ 0% on 8 cores (4 cores  X2 with Intel HT turned on).  I have to stop pressing a key if I want  the syntax/inspection parse to complete.

The desired behavior is  that if a file is not being modified, then the syntax/inspection parse  should continue for the file in the Editor pane using n cores - 1.

Thanks, -Alex


IDEA-14683 Optimize Editor Syntax/Inspection parse for multi-cores, limit autoreparse delay to only 1 out of n cores.

1 comment

On 10/09/2010 11:09 AM, Alex wrote:

IDEA pauses the syntax/inspections parse on key presses when the file
is not even being modified. Clicking on the editor pane with your
mouse  also pauses the syntax/inspection parse. (However, just moving
your  mouse over the editor panel (no clicking) does not pause the
parse.)


This has been a major pet hate of mine as long as I can remember.  It's
easy to repro, just make a modification to a file and then keep moving
the cursor around, either using the arrow keys, or clicking the mouse.
The file will never finish reparsing.

I'm sure there must be a deep down reason for this as it seems it would
be a major failing otherwise, and would have been fixed by now.

Perhaps someone from Jetbrains could explain why it works this way?
If not, should we submit a JIRA?

N.

0

Please sign in to leave a comment.