I'm switched to idea from eclipse recently,the biggest question which make me uncomfortable is the auto popup completion is a little slower then eclipse.
In setting page,i set all possible delay to 0 but it's still slower than eclipse.
And i have noticed that if something(field,method,class...) be reference after first time,it's prompted to be faster,but after a few secends,it's will become slow again,maybe 100~300ms
The eclipse auto-completion is nearly have no delay when i set delay to 0,so how do i raise the speed of idea code auto-completion?
Related
I set the editor.cursorSmoothCaretAnimation to true in Visual Studio Code but the cursor lags behind when I type/select/delete text quickly:
I turned off all the extensions in VS Code by running code --disable-extensions in terminal but the problem persists.
How can this be fixed?
I Found a Solution
tl;dr: I had set editor.smoothScrolling to true. Disabling that option (mostly) solved the issue:
The cursor does not stutter as much in person as it might look like it does in this gif. There is still a little bit of lag - about 1 to 1.5 characters, but not more than that. This is actually the same amount of lag I was seeing when every extension was disabled and all settings except editor.cursorSmoothCaretAnimation were commented out, which tells me that the lag can't be reduced any further (or at least I can't reduce it any further).
So how did I arrive at this solution?
Initially, I had disabled extensions temporarily by running code --disable-extensions in terminal but that didn't seem to solve the problem. So, I went ahead and manually disabled each extension (globally) and also commented out all my settings in the settings.json file, except editor.cursorSmoothCaretAnimation. Thankfully, I found that the cursor lag had reduced to about 1 to 1.5 characters. As disabling all the extensions had not solved the issue before, I had an inkling that my settings were to blame for the lag. Thus, I began going through each setting and began uncommenting them, one by one, and checking to see if the lag had returned. Finally, I found that uncommenting the editor.smoothScrolling setting reintroduced the bothersome lag. Hoping that that setting was the only one causing it, I uncommented all of the other settings and enabled all my extensions. To my surprise, the lag did not increase any further. Later on, I did a few checks and I can confirm that editor.smoothScrolling is the setting to blame for this.
Why?
Why this happens, I do not know. I will be opening a new issue about it in the VS Code Github.
Disabling Save Typing extension has solved the issue in my case.
I'm using Eclipse Kepler (4.3) (with pydev, in case that matters). If I collapse my code (using Ctrl-9 or the Source menu) and then selectively uncollapse only the part I'm working on, it works fine for a while. But at some point in the session, I'll notice that Eclipse has randomly (?) decided to uncollapse all the code. Am I doing something wrong, or is this a known "feature" of Eclipse? And is there any way to prevent it?
And in case there's no way to prevent this, I have a follow-up question: Is there any way to collapse just the code I have selected? I.e., can I select a set of functions and collapse them all at once rather than going through and collapsing them one at a time?
I started to use the Eclipse Kepler this week and there is a new feature which is annoying me a lot.
When I'm in a Debug Perspective with the source screen maximized, some times, the Debug Screen opens over the source code. This behaviour bother me because the Debug Screen covers the code making it impossible to see.
Anybody knows what do I need to do to disable this feature?
I agree that it's annoying but the behavior as been in eclipse for many years...
You have two options; restore the Debug stack (just hit the restore button on the element in the Trim) or drag the trim element to the right side trim. If you do the latter then even though the Debug view will still open it's less likely to obscure the code.
So, I'm working on an Eclipse Plugin which includes a custom view based on analysis of source code. The majority of the time, it works great. However, if I quit Eclipse with that view open, when I reopen it, it runs into an error with either IWorkbenchWindow.getActivePage() or IWorkbenchPage.getEditorReferences() returning null. This inconsistency seems to be because the view has the focus when Eclipse quits and is the first thing that Eclipse tries to reconstruct on start up. the focus is on a non-window shell (I don't fully understand this, but that's what this said). Is there a workaround so that I can ensure that Eclipse fully loads its IWorkbenchWindow before my custom plugin regardless of what has the focus when Eclipse closes?
Thanks
You can consider using the site instead: getSite().getPage()...
Tonny Madsen pointed out in the comments that, from within a View, I can access the Active Page from getSite().getPage(), which solved the issues.
Since a week or two, Eclipse becomes very slow after resuming Windows:
Scrolling becomes very slow: the scrollbar and line numbers scroll at a different speed than the text. Then I need to wait for the text to catch up.
Typing is very slow. I'd guess there's a 500ms delay
Running code is very slow. The unit tests for my current project typically take around 5 seconds. After resuming Windows, this is systematically over 20 seconds.
Opening or saving a sourcecode file takes longer (several seconds)
However, navigating menus doesn't seem to be slower than before.
Restarting Eclipse doesn't help, though I notice it starts up quicker than after a clean boot, which makes me believe it doesn't shut down completely.
Other Java apps don't appear to be slower.
In case the problem can't be found, is there some way I can force Eclipse to restart cleanly?