I've been using VS Code in "VIM mode" for years now without a problem. I'm on v1.46 now. I fired it up today and immediately couldn't type and other keys like escape failed to register. In the lower left corner, I'd intermittently see the following:
I went into extensions and disabled the Vim Emulator which now allow me to edit the file normally... without the vim functionality, of course.
I saw a bug filed through GitHub that looked like it might have addressed it, but it was closed due to lack of info provided.
Any ideas what might be going on or how I can get my vim functionality back?
UPDATE
Here's a bit more info:
I reinstalled and updated both VSCode and plugin - same behavior
Sometimes the whole thing failed from the get and other times (after restarting), it seemed to fail 1 key at a time - for example I'd be typing along and then all of a sudden hitting backspace produces an error message in the lower right corner to the effect of command 'extension.vim_backspace' not found - here's the closed issue on github - https://github.com/microsoft/vscode/issues/22365 for that specific message, but I also got errors with the escape and other keys
I also tried switching to NeoVim (on mac) which I thought was working, but eventually ended up going the same route (esc stopped working first typically)
I was having a similar problem with Vim in VS Code, and I noticed at the bottom-left when it reads --NORMAL-- or --VISUAL-- I typed the letter "i" and --INSERT-- appeared and allows me to type. I typed "i" because when I could type that is what I saw in the bottom-left corner of the screen.
Hope this is helpful.
Related
I have loved Edge and have convinced others to use it - until 2 days ago. Out of the blue I can no longer begin typing a web site in the address bar and have it autofill. I have to type every single character.
I went into settings and found one called "Show me suggestions from my typed characters" and "Show me suggestions from history" but both are greyed out and cannot be turned on! And they say "This setting is managed by your organization."
I have tried everything to fix this - including going back to the previous Windows.
I was going to actually uninstall Edge but found out I CANNOT DO THIS! This is crazy. Then - when going to uninstall Edge - I saw what might be the culprit (though I have no clue - I'm not an expert). On October 7 something called "Microsoft Edge Update" was added and probably part of a Windows update and is in my list of add/remove programs, which of course as I stated above, cannot be done. I will disable Edge and stop using it if I cannot get this fixed.
What's going on? And there were a few other weird glitches, like the most commonly used function for me is alt-tab and that was taking me weird places. Can you please help me?
Same thing happened to me at the same time. Just delete the keys besides the default one in the following registry path:
HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge
Just delete the keys besides the default one in the following registry path: HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge
This worked for restoring the autocomplete function but my Edge still claims it's managed by an organization while it's installed on a home PC. I installed the insider beta just to install another version of Edge and it has the same issues.
I am used to the focus follows mouse option for years.
In the VSCode editor I want to switch between the integrated terminal and the code writer by simply focusing the cursor on them.
For example in Geany editor:
Does anyone know how to enable focus follows mouse from settings or using any simple hack while trying to move between the code writer and terminal?
The simple answer is it's not possible at the moment. There have been numerous issues raised in the past (#25685, #44214) and they have been closed because "the number of votes ... and duplicate issues" are not high enough. Go out and raise an issue and get others to vote on that issue.
There was a pull request made a couple of years ago that would introduce a focusOnHover setting. This appears to resolve the issue but it has not been accepted and is now a bit stale and needs some work. So you could for VSCode (for yourself), apply the pull request and then build it.
I am keen on this feature as well.
It is now a candidate for the backlog, see https://github.com/microsoft/vscode/issues/93772 (Provide a "focus-follow-mouse" setting)
So upvote it if you want this. It needs 20 votes to move to the backlog.
In VS Code 1.10.2 running on macOS Sierra (10.12.3), whenever I type an open paren ( ( ) followed by two spaces in quick succession, a period ( ( . ) is inserted in my code. If I type the spaces with a momentary delay in between, nothing happens (no period is inserted).
I recently reformatted my hard drive and reinstalled my OS, so I know I'm working with a very clean box.
I've got 4 plugins installed: Apex, ESLint, ForceCode and Visualforce. I tried disabling all of them and reloading my editor, but that didn't fix the issue.
Is this a bug, a configuration setting, or something else? It's getting really annoying, so I'd like to find a way to make this stop.
I found the answer. Apparently this is a new MacOS Sierra feature. It's supposed to be turned off by default, but apparently it was enabled, perhaps because I installed a clean copy rather than upgrading.
You can disable this feature by opening Settings > Keyboard > Text and unchecking the "Add period with double-space" option:
Why on earth anyone would have thought that this feature would be useful I cannot fathom. It doesn't make sense in the context of sentence (since it places a space before and after the period)... but there it is.
Using Visual Studio Code I have installed a few extensions (like Guidelines showing vertical dotted lines between pairs of matching brackets). When I start VS Code I can see all my extensions working fine in the Editor window.
However, when I switch to another tab within VS Code, I no longer see the Guidelines or evidence of any extension working in the new editor tab. Worst of all, when I then switch back to my original tab, all the guidelines etc that were there a few seconds ago are gone!
To fix the issue I have to restart VS Code. This can't be right! Has anyone hit the same problem?
I have tried uninstalling VS Code where it warns me some components could not be uninstalled and I have to do them manually. It doesn't tell me which. When I then reinstall, the extensions are visible (without me reinstalling them) but again I hit the same issues as above.
Please help?
Seems like having too many extensions installed, or perhaps one that is misbehaving behind the scenes, causes this problem. Reduce the number of installed extensions. Use Help->Developer Tools -> Console to see if there are any messages relating to the Extensions server
Bounty Update
I am leaving the question essentially the same, but I just want to point out at the beginning here that I'm most interested in help trying to get the socket between flash (Adobe Animate) and the native debugger working again, as I believe that is the issue I'm having. Or is it a socket between flash and Windows?
Original Question
I've apparently turned something off? Even when I write really bad code (like trying to call a function that isn't there or divide an integer into a fraction), the flash player boots, shows a background color and stops there. No messages in the output window or compiler errors window. If I fix my code, it all runs fine, but for about 30 minutes (ever since I started trying to work with bitmaps for a sprite sheet) I get no runtime errors no matter what kind of mistake I type in my code. Anyone know how to turn it back on?
I've checked my actionscript settings and I have both warning mode and strict mode checked on.
Could it be a socket issue? I admit I have little to no experience working with sockets and only a surface understanding of what that even means. I've added the socket tag. If someone can see that this is clearly nothing to do with sockets, by all means, I'll remove the tag.
UPDATE: 6/22/16
I just reinstalled Adobe Animate CC 2015.2 and no change. I'll try compiling it in flash builder when I get a chance to help pigeon hole the problem. (Edit 6/24: flash builder worked! But my trial version expired the next day so is no longer a viable option).
And I just tried something in the command prompt in Windows 10 as an administrator:
netsh winsock reset catalog
netsh int ip reset reset.log hit
which I found another user on flashdevelop.org used to fix a similar issue, but no change.
And I just tried debugging in Flash Builder. It worked fine (debugger caught bugs) but my trial version expired the next day.
update 6/24
I've tried launching debugger for AIR from within the Adobe Animate CC IDE and it works fine if there are no bugs; it fails to do anything visible (no Iphone emulator, no swf window) if I put a typo or error in the code.
I also just deleted winsock and winsock2, rebooted Windows, then reinstalled winsock and winsock2. No change.
update 6/25
Just tried a system restore in Windows to set all my files and settings and drivers etc. to the way it was a week and a half ago... Also completely uninstalled all Adobe products and reinstalled. No change. I can only imagine that wiping my hard drive and reinstalling Windows would do the trick, but come on, it hasn't come to that has it?
As VC.One suggested, I checked the compile error window (cannot believe I didn't check before! Maybe when I checked before there were no compile errors... Only runtime errors?) and the errors are showing up there. Does this mean that it's catching compile errors but just not runtime errors?
When you force/test a runtime error... make sure you check
Compiler Errors (ALT+F2) and also Output (F2). By Output I mean the window that shows traces (and runtime issues). One of those two should have some feedback for you.
A possible solution is to save a new Workspace. So with those windows for Compiler Errors and Output both open (or tabbed, I tab them next to my Timeline) go to Window (in top options like File/Edit/Debug etc) and choose Workspace, then into that you choose New Workspace. Give it a name in the pop-up and okay everything.
Flash should always load that current workspace (next time, go to Workspace option again, check that your specified workspace [by name] has a tick next to it...).
Possible pitfalls:
1 - Use the debug player
2 - Make sure there isn't somewhere a try/catch enclosing the portion of code that triggers the event that may lead to an error
3 - Socket issue: may be exported in debug mode but swf cannot connect to debugger (it waits in a blank state for 60 seconds I guess)
4 - Does it compile ok? If there are compilation errors you may get an SWF anyway but then it will not start
...