Just a little annoyance :
Context :
The content assist is set up and work most of the time.
But I just tried to write document.getElementById;
Problem :
The problem is I cannot select one of the proposals for document.get: when I select an entry,the popup disappears and nothing is inserted in text.
I noticed that it is preceded by a green dot. Other proposals with a blue triangle are inserted normally.
Any hint why I cannot make it work ?
Thanks,
UPDATE :
Eclipse 3.8 debian
It sorts out that the culprit was the option "guess filled functions argument". It messed up everything. Now I'm back to work (as expected).
This feature is disabled by default, but if, like me, you set it up and forgot about it, here is how to disable it :
Windows -> Javascript -> Editor -> content assist -> guess filled function argument
It should be disabled.
I've found that on sometimes the assist pop-ups can be finicky. Pop-ups can be in either selected or unselected states. If the pop-up is in an unselected state clicking the actions sometimes does not either work or the option can be incomplete.
Try testing and making sure that the pop-up is selected before you choose an option. (The pop-up border should change and you may get a scroll bar to indicate the difference.
Related
When I right click in the editor, vs code executes whatever menu item the cursor happens to be over. It happens far too fast for me to make my actual choice known.
I have already spent 30 minutes trying to find a solution. If you search for "right click" in the Command Palette, you are told there are no matches. You don't get any hits in the docs, either. Please advise. Thank you.
It has been reported that the situation you mentioned is a bug in the repository on GitHub. It is reported that Visual Studio Code works fine when zoom is disabled.
You can update the following setting to override this behavior:
"editor.mouseWheelZoom": false
Or you can update the mouseWheelZoom setting from the pop-up window by using the shortcut CTRL + , to go to Settings.
It's crazy, but this is still an issue for Linux users after so many years. Especially, when using a Laptop with touch-pad it makes VSCode frustrating to use. The problem occurs when you use "native" window style (you can tell, because the theme will not be applied to context menus) and have a non-default zoom.
The GitHub issue that #sercan linked to has a few solutions. In order to save you some time, there is basically two things that I found work and make sense:
Set your zoom level to default / 0. In settings.json add: "window.zoomLevel": 0 This works with all window styles, but obviously is not always viable
Change the title bar style from native to custom. In settings.json add: "window.titleBarStyle": "custom" This will change how the title bar but also the context menus look. Setting this, you can zoom in again
I recently, too-trustingly, upgraded my Sublime Text 3 to Version 4 (Build 4107). Now auto complete behaves completely differently. It now has a pop-up from which I must select a choice - before I would just hit tab and it would choose the best option for me (I could then tab again to try for a better answer).
A concrete example: before, when I typed a word with a typo, for example "questino", I could, with my cursor directly after the o, hit tab and it would correct it to "question" automatically. Now it doesn't do that - now it would pop up a list of any longer words, such as "questions" and "questioned", and then I would have to arrow to one of them and hit enter. It wouldn't even give me "question" as an option - I would have to backspace over the n and then hit tab in order to get a popup that included that word, because not only is the popup annoying, with it requiring multiple additional keystrokes, but autocorrect no longer corrects to a word of the same length as my currently misspelled word, only to longer ones.
There are a lot of options in Preferences, including: auto_complete, auto_complete_size_limit, auto_complete_delay, auto_complete_selector, auto_complete_triggers, auto_complete_commit_on_tab, auto_complete_with_fields, auto_complete_cycle, auto_complete_use_index, auto_complete_use_history, auto_complete_preserve_order, auto_complete_trailing_symbols, and more.
Does anyone know the precise set of preferences to make it behave exactly like it used to? Or maybe there is a package that fixes it? Or maybe my next step will be reverting to the previous version.
Thanks.
The closest you can get right now appears to be:
"auto_complete": false,
"tab_completion": true,
"mini_auto_complete": true,
This is still different from how ST3 works. Tab will fill in only a single value, pressing tab again will not toggle between options, but it won't have the distracting popup.
Background context on the forum. Hopefully this answer will be quickly invalidated by an update or plugin.
Coming from Visual Studio and starting a project in Java, I realized I couldn't cope with having to press ctrl+space to have the autocomplete panel show up. An easy workaround was to set all keyboard characters to be trigger characters for autocompletion.
My only problem is that, when presented with autocomplete suggestions, a single press on the space bar will write the first proposition. In situations where I'm happy with the suggestions, that's just fine. In situations where I actually want to use what I wrote down initially, I have to press 'escape' first to remove the autocomplete panel before I can press 'space' safely.
Netbeans doesn't use the space bar as a validating key for autocompletion (only 'enter' does that) and I like that behavior. Any way to replicate it in Eclipse?
Thanks in advance for your answers!
EDIT: I should have mentioned I'm using Eclipse on the Mac.
Guillaume
I have the same problem with Eclipse Indigo on Windows XP actually. Coming from intellij idea, I also felt the need to set the whole keyboard to trigger auto-complete.
A quick proof that SPACE key does accept suggestions : type inte on a new line. If the auto-complete menu shows, press SPACE. It goes for Integer.
If anyone knows how to set the SPACE key to "ignore suggestions", it would be great, because the escape key on my keyboard is also too far away :)
Thanks
Edit : actually the best would be to have only the ENTER key validating, because ';' and '(' also seem to validate
I just tried to reproduce your behavior, but couldn't. Here is the configuration I have (and the steps I have done to reproduce):
I have installed Indigo (current version of Eclipse, version number 3.7).
I did not change any configuration there, this is what is the default:
Under Window > Preferences > Java > Editor > Content Assist, I have the following settings:
Completion inserts (instead of overwrite)
Insert single proposal automatically (which is ok most of the time)
not insert common prefix automatically
I have a simple class, go down to a method, and do the following steps:
Enter this.no and wait some time. Sometimes I have to press CTRL + SPACE, sometimes not.
Proposal pops up which includes notify and notifyAll.
I press SPACE and a space is inserted in the text, the autocomplete suggestions are closed without inserting anything.
I do not know if older versions of eclipse have the same behavior.
At a break point my Eclipse used to show me the value of a hovered variable, now it only shows the type name.
How can I turn that back on?
Go to the preferences and type "Hovers" in the search box at the top. Make sure the Combined one is checked. Though I have found that even if they are set correctly sometimes (in the case of certain fields) it shows only the type, not sure why that's the case. You might want to ask about that in the Eclipse JDT newsgroup.
Seems like Ubuntu can intercept some of the Special Key presses.
Sometimes when I jump into source code, e.g. from search or when looking up the declaration of something, the Eclipse text editor tries to display nearby long lines by horizontal scrolling. This happens even if the item I jumped to is well within the display without scrolling. I find this rather annoying, so:
Is there a way to disable this? I have searched in vain through all the editor settings.
Specifically, this is about Eclipse CDT, but I suppose the behaviour is the same in JDT.
This seems to happen in other eclipse editors too (like PDT for PHP)
It could have been related with the ScrolledFormText, but the Plugin Spy tells us a WorkbenchWindow class is concerned, as well as an AbstractDecoratedTextEditor, that is in essence an org.eclipse.ui.texteditor.AbstractTextEditor.
The source of that AbstractTextEditor indicates having:
a ScrollLinesAction for vertical scrolling
a TextNavigationAction for settings the cursor and potentially triggering horizontal scrolling
I am not sure how to change that behavior, except by contributing somehow to the active editor identifier (for instance, for java, "org.eclipse.jdt.ui.ClassFileEditor"), and modifying that Action.
I was having the same issue and found these open bugs for it on the Eclipse Bugs:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=314208
https://bugs.eclipse.org/bugs/show_bug.cgi?id=321189
You can prevent it from happening when you switch the Code Folding off and reload the file.
grtz,
T
right click on your eclipse shortcut and choose properties. in compatibility tab choose "windows xp(servicepack 3). http://www.vistax64.com/vista-general/133849-disable-dynamic-horizontal-scrolling-vista.html