I am new to Visual Studio Code. I have used it lightly in the past but need to use more heavily now that I am working with Python. However, the API Key bar keeps coming down when I am typing, trying to create a new file, etc. Does anyone know how to stop it from dropping when ever it feels like it?
Try and restart the platform and then re open the file I had that error a bit ago when working with GoLang but opened a python project up and that seemed to fix it
If this happens, there is an extension called WakaTime. Uninstall this extension and everything goes back to normal.
In XPages, when I try to open a .js or .jss file, I often get just the tab wirh "Client/Server JS Editor" and nothing else, i.e. the file doesn't load. From the Navigator Eclipse view, I can open the same .js or .jss file using any other editor without problems. And then, it sometimes works, but I don't know yet when it does and when it doesn't. The other Editors are okay by the way, .lss opens nicely.
This behaviour I get for a few weeks now. Since it started I reinstalled Notes a few times, I upgraded to FP8, I also reinstalled Windows10 and Windows10 upgraded me to the Creators Update (with the fix, in the end). There's nothing that explains to me why the file doesn't show up on the screen.
Anyone familiar with this? Could you please tell me how to repair this?
Thanks!!
It's a bug introduced with FP8 that is fixed in FP8 Interim Fix 1. See this document for download options for FP8 IF1.
As a workaround you can do a clean/rebuild of the nsf and then use the SSJS editor.
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
I am using Visual Studio code and it works fine except that double clicking the file doesn't seem to open the file. Instead the Program just opens with an Untitled.txt screen.
Right click -> Open with code also works.
How do I make it work? I am using Windows 8.
This wasn't the case some versions back, but now it seems, that it actually is the expected behaviour. The developers intentionally do not register VSCode as the default open handler (don't ask me why).
But maybe there is a workaround. Try the following steps:
1. Try to associate the filetype(s) with another app, and then again to VSCode.
2. If setting to other editors and returning to VSCode still opens Untitled-1.txt, then you could
3. try reinstalling VSCode, and then reset it. When resetting, confirm that there is only one VSCode in the choice list.
It also could be, that you'll need to reboot your machine. Finally, you'll possibly also want to take a look at this issue on GitHub.
Hope you can solve it this way.
So I'm starting to guess Javascript wasn't the best choice for VSCode to be based on. It is pretty much the same as SublimeText and even slower, though the debugger and code intel is awesome and far beyond Sublime's capabilities.
The thing is I suddenly got a chrome-like inspector frame on the right side of the window, which caught my attention and got me googling about it (too bad almost nobody is talking about vscode yet so it's a pain to even find some info), and found out another person got the same weird issue. Somebody told him that F12 opens the inspector like a normal web app so you can look under the hood (which os most likely bullcrap since it makes no sense, probably just a bug).
The thing is I decided to test out keypresses, and discovered Fn+Shift+Cmd+F12 opens a new window with a weird button and a web inspector, which has no utility at all, but it's there so I got curious and messed up with it for a while. Bad idea since it crashed the entire app.
All this story has the point of warning about how Javascript is not as stable and independent as Objective C, since it's obviously working on top of V8 and Webkit and whatnot, any of which multiply its chances to crash.
Sublime has also crashed for me a couple times, but it does Atom Saving (operating system's native autosave that stores every change in the filesystem so app crashes don't affect the files).
VSCode is not native and is in a very alpa state (version 0.1.0 as today), so this is kind of a feedback for them and a warning for other users, posted here because there is a link for this stackoverflow community on their website, and is the only community-driven way of feedback they have.
I wish they open the development so others can contribute or, at least, do like SublimeText which isn't open but supports extensibility thru plugins and python console.
Now, the question:
Is there a way to make Sublime plugins work here?
The keybindings you have found are used by us internally to debug VSCode quickly in case we notice a problem. We simply forgot to remove them, kind of like how Ctrl+Alt+Delete happened :).
We will remove these keybindings with our next update, to avoid confusion, in a couple of weeks.
We have plans on supporting plugins, we have made progress on this story, but we were not happy enough with the API, and we decided to further validate and improve it before making it public, to avoid as much as possible future API breakage.
As for the actual question, it is not possible to run Sublime plugins in VSCode, for similar reasons why it is not possible to run Sublime plugins in Eclipse or in Visual Studio. There is, however the possibility of code sharing between plugins developed for different platforms, see for example Omnisharp, which is shipped with VSCode and for which there is a Sublime plugin.
You're complaining about VSCode being created using HTML, CSS and JavaScript and not something like C# or Objective C. You do realize that since day one the following Apple apps were made with a similar hybrid approach of Objective C and HTML, CSS and JavaScript. These are apps that millions of people use: iOS: iTunes app, iTunes Store app, App Store, and on desktop: iTunes, App Store.
Visual Studio Code is a preview, meaning something that just left alpha stage development and is in early, early, early beta, like just a week ago. So there are lots of things that are still missing or not totally working yet. The Visual Studio team is working at three-week sprints and intend to update the product at that pace, so if you've downloaded it, don't expect it to have every possible feature yet. This is a preview. Explore it. If it doesn't fit your current workflow, don't use it. Stick with what you have. But keep an eye on it because it will evolve steadily over the coming months.
I tried F12 in VSCode on windows and it opened the Dev Tools window, which makes sense since it's built on GIT's open source editor Atom & Chrome.
Sublime plugins? No, you can't use ST3 plugins in Atom, but hopefully we'll be able to use Atom plugins in VSCode once plugins are included in VSCode.
At the moment VSCode don't have any functionality for plugins, but it's coming soon see forum
There is also menu item under help in VSCode for reporting issues and suggesting features.
Me too would like Plugins for VS Code. As I would like a WakaTime plugin as I'm spending so much time working in it :). Both on Mac as in Windows.
I also discovered F12 one day but just thought: 'wow pretty cool!' and nothing more. But hey, I'm a webdev.. :)
It's now october and it's still there. And I hope it will stay. Just like crrl+alt+delete. #Sebastian I agree with #JimmyBoh, the whole preamble of this question is probably better suited to be put on a forum. Otherwise this question will probably be closed as 'not constructive'. To prevent other non-answers like this one :).