Totally transfer VSCode settings from one Mac to another - visual-studio-code

VSCode is wonderful but it takes a little careful setting-up.
There are numerous secret tips to follow, example
How to turn off "matching" highlighting in VS Code?
https://stackoverflow.com/a/59225110/294884
and so on.
If I have everything "just right" on Mac A, how can I perfectly transfer all the detail to Macs B, C, and D?
For that matter, how could one transfer their VSCode settings to a Windows machine from a Mac?
Note, now includes in VSCode from 2021...
Another amazing new feature added to VSCode:
https://code.visualstudio.com/docs/editor/settings-sync

I use the vscode extension Setting Sync. It uses github to sync everything up, it should be platform agnostic and works like a charm.

Related

vs code consistent keybindings for Mac and windows with settings sync

I use a windows computer for work and have painstakingly set up many keybindings for common tasks, as well as many other personalizations I really would like to have transferred to my personal computer, which is a Mac.
I recently found out about and set up Settings Sync, which is pretty awesome, but I can't seem to get my keybindings to work quite how I would like.
First, it doesn't seem that any of my keybindings transferred--when I open up the keyboard shortcuts on Mac and display User Keybindings, the list is empty, yet when I do this on Windows, all my keybindings are there.
To complicate matters, I sometimes use a Windows keyboard with my Mac. Without getting into too much detail, I'll explain what I'm trying to accomplish with a particular shortcut:
On windows machine, I use the right alt and ctrl keys to open up my integrated terminal with:
alt+ctrl+t
I'd like to keep this keybinding to work even when on my Mac because when I use my windows keyboard with it, I still have the alt and ctrl keys on the right side of the keyboard.
However, on my Mac without the windows keyboard, in place of the alt and ctrl keys I have the cmd and option keys, so in this instance I'd like cmd+option+t to trigger the integrated terminal.
So, is my solution to simply recreate all my windows shortcuts that use alt+ctrl with a corresponding cmd+opt version for Mac? And what about all the missing user keybindings that didn't seem to transfer with settings sync (logs show that they should've been transferred)? If anyone has any advice about how to properly set this up, I'd greatly appreciate it. Thanks.
It seems that Settings Sync synchronizes the user’s shortcuts by platform, which would prevent conflicts between Windows and Mac. So to achieve what you’re looking for, it should be enough to properly configure your shortcuts as you want them to be now in Mac.
There shouldn’t be any conflict when you move to your Windows machine, each platform should keep its own configuration :)

What is the difference between many cursor-word-related commands in VS Code?

I am customizing cursor-word-related commands with new keybindings. And there are many cursor-word-related commands in VS code. I know the command with Part has something to do with _ in words in a VS Code GitHub issue. But what is the difference between all the other commands? Say, what is the difference between cursorWordLeft and cursorWordStartLeft?
I have been googling for a while, but I cannot find docs or anything official on this topic. And it is really timing-consuming to test out every command. So is there anything on this topic that I can look into?
Also, which two commands correspond to the operation we normally do with Ctrl+Right and Ctrl+Left on Windows?
I'm going to answer your question partially. The difference between cursorWord vs cursorWordStart is that cursorWord is what the VSCode developer team created for the VSCode editor (they can make it work however they want). While cursorWordStart is essentially what Visual Studio IDE uses and it was added to VSCode, made to work exactly the same (so they don't touch it).
My answer is expanded upon what Alex Dima posted on GitHub (a Microsoft developer working on VSCode). I don't think it gets much more official than that. Source

VS Code - changing tab disables extensions. What am I doing wrong?

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

VSCode plugins and thoughts on alpha release

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 :).

Voice coding in Emacs on Mac OS X

I would like to be able to write code by voice recognition and him currently using Aquamacs 2.4 and Dragon Dictate 2 on Mac OS X 10.6.8. Does anybody know if this is possible and if so how? I've seen shorttalk, emacs listen, and voice code but they only work on windows machines with Dragon Naturally Speaking.
Any leads would be much appreciated.
Also I am writing in R via ESS.
Have a look at this presentation by Tavis Rudd : http://www.youtube.com/watch?v=8SkdfdXWYaI
He runs Dragon Naturally Speaking inside a Windows VM, because the Windows version can be scripted with Python. Then the VM communicates with Emacs on his local machine.
He says in the presentation he will open source his code, but it doesn't seem to be there yet on his Github.
So yes, it's possible, but at this point there is no out of the box solution. If you really want this, prepare to invests weeks or months to get to a properly working setup.
I recently released the coding-by-voice solution I created to solve my own RSI issues. It can be found here: http://www.voicecode.io
I use it mostly for coding in Sublime Text and Xcode, but it works great with emacs or vim as well. The great thing about this solution is that all commands can be chained into "command phrases" so you don't have to pause between every individual command like you do with other voice command solutions.
It has builtin support for all standard variable-name formats (snake case, camel case, etc), has builtin commands for every permutation of keyboard shortcuts (ie command-shift-5, command-option-shift-T, and so on), has cursor movement commands, app switching commands, window switching commands, commands for symbol combos like "=>", "||", ">=", etc, and tons more. Plus it is very easy to add your own custom commands as well.