I am quite new to vscode, and am trying to figure out how to solve the following issue:
I use vim bindings (via vscodevim), and am happy with it
I have custom bindings for the main language I develop in (Coq) that I am adamant about keeping and that are of the form ", n", ", u" and so on. These shortcuts are not used to edit code, but rather to interact with the prover.
This setup currently entails that I globally cannot type a comma anymore, which is quite annoying :) I hence would like to disable these shortcuts when in insertion mode.
I have tried to add the condition !vim.insertModeKeyBindings to all When fields of these custom bindings, but it does not seem to be sufficient: pressing , still triggers a Waiting for second key of chord... even in insertion mode.
Would anyone know how to solve this issue by any chance?
Best,
Yannick
Related
How can I toggle on and off the display of Type hints in VS Code? For example, I've got the code .remoteOf(ClassServiceClient.class) and what I see is .remoteOf(CLAZZ:ClassServiceClient.class) but I can't actually select or seem to interact with the CLAZZ word.
How do I toggle this on and off? It seems useful in certain situations, but it just makes me think I typoed something.
I'm sure this has been asked before, but I haven't been able to come up with a word that seems to describe this feature.
This feature is called Inlay Hints and can be found under the Editor section.
After this, I've gone from displaying clazz:#Log4J2 to #Log4J2, and have enabled the option to display this hint by holding down a set of keys, ctrl + alt by default on Windows.
I am using Eclipse Juno, and none of my keyboard shortcuts (e.g. Crtl + *) function at all. I checked in preferences and they're all still set they just don't do anything. This is really annoying, particularly with very commonly used ones like undo and redo. Does anyone have any ideas on how to possibly fix this? Thanks!
The problem's solution ended up being pretty simple, kind of similar to the question linked by #Apprentice but not quite, apparently whoever had been using the program before me linked CTRL+Z to another command as well as undo, so I went to (Window->Preferences->General->Keys) and unlinked it manually, now it appears to work.
One of the common issues (if you're using Windows) is accidental swtich of keyboard layout by pressing [ctrl]+[shift]. You can try using this combination again to see if it helps.
If it doesn't, you may want to have a look at this question: Undo shortcut not working in Eclipse
I'm wondering if I'm the only one struggling (i.e. failing) to keep the emacs key bindings working in Eclipse.
I set them. It works fine. The it stops working fine. Some keys still work, others don't. I find myself in a kind of weird quantum state of uncertain key-binding setup superposition. Some key bindings from the standard set work, some from the emacs set work, some things I can achieve with neither set of bindings.
I'm the only one to experience this? I've seen this on at least 4 computers in the past few months.
I set key bindings back to standard set. Sometimes it works. I use the reset to defaults button. Try to set it back to emacs. Doesn't work. Pressing the apply button between the different steps or not... Drives me crazy.
On some computers, the bindings are just whatever. Can only save using the mouse, C-d and C-k don't work to delete/cut lines, most emacs keys still work but back to C-space for auto-completion, etc.
Anyone knows what can cause this? How to prevent it? Am I pressing some key binding key-bindings by mistake?
I had a similar problem with the Ctl-K, Ctl-D commands: after doing an upgrade (I forget whether it was Eclipse itself or the Android plugin) I saw Eclipse offering a little pop up menu on both these keys, offering to do either the correct Emacs command or some completely unrelated command. So, for example, Ctl-D offered to either delete the next character (correct) or delete the line (incorrect).
After some poking around in the key bindings (Windows>Preferences>General>Keys), I discovered that sure enough, someons in the Eclipse project supplied these wrong bindings in addition to the correct ones. So I deleted the incorrect bindings and left the correct ones.
So I thought I would be out of the woods at this point. But I also discovered that I had to add the correct binding back in a couple of times before it would stick.
Look for Cut to End of Line under the Command column and make sure it has Ctl-K when Editing Text and in the Text Editing Category. The same for Delete Next (which means next character). But make sure Ctl-D does NOT show up for the Delete Line Command.
Test it out in an editor window; if it fails, go edit the bindings again, test again, repeat until it sticks, making sure you click Apply after editing the bindings.
Recently, I need to use Eclipse instead of Netbeans.
I find the following issues is annoying in my case. Say, I key in the following wrong method name.
So, I tend to fix the error, by deleting the wrong method name (But not parameter, as I know I want to pass in true), including the dot. I key in dot again, Eclipse auto completion will prompts me list of methods
I am happy with the suggestion. I press ENTER. However, this is what I am getting.
Now, I need to manually deleted the uselesss (checked). This is pretty annoying, especially when the method takes in 4 to 5 parameters. I have to delete them 1 by 1.
I consider this a usability defect. I do not have such issue in Netbeans. Anyone of you know any workaround to overcome this usability issues? Is there any options I can turn on or turn off?
You can also press Ctrl+Enter to insert the completion which will 'replace' the incorrect typed word.
Look for "Toggle between inserting and replacing content assist" in http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.jdt.doc.user/tips/jdt_tips.html
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.