![]() ![]() ![]() From there you should be able to install all your shell integrations and command line tools with no problem. Check the option and don't worry about it. There are alternative solutions, but I found this to be the easiest to implement and the most out-of-sight-out-of-mind solution. Before doing anything, go to your Applications folder, right-click on iTerm, click 'Get Info', and check the 'Open using Rosetta' option.īefore I did this, I was getting a bunch of undecipherable errors from various command line tools because (presumably) they have compatibility issues with the M1 chip. Once you install iTerm 2, you'll probably want to install Homebrew, Oh My ZSH!, NVM and whatever else. UPDATE: Visual Studio Code Insiders just released a version compatible with M1 Macs! Link: VS Code ARM64 If you were using a custom font (Fira Code, Dank.sh, Monoid, whatever floats your boat) go and install that. All of your extensions will get installed, your settings will be synced, and you'll be set. ![]() Once you've got your settings from VS Code on your existing machine synced up, install VS Code on your new machine, enable Settings Sync, and.sync your settings. zshrc in a Github Gist or something of the sort. Enable Settings Sync in Visual Studio Code and sync your settings from your current machine.But it doesn't have to be entirely terrible! And going through the process of resetting an M1 Mac product is a pain¹ in the² ass³, so I'm attempting to save you the headache.īut I restored from a backup and mine works fine! While some things worked, other things went horribly wrong. I was gifted an M1 Mac Mini (thanks, girlfriend!) and tried to set it up with a backup from my Macbook Air. Because some stuff doesn't 'just work' when restoring from an old backup. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |