I’ve been using this along with the other extensions bundled with VSpaceCode and it has been an awesome experience (and has brought me back to VS Code from Spacemacs). Just want to say thanks for writing this extension and for bringing the magic of Magit to more people.
I didn’t know about the forge features, will check those out.
Same, I recently was on a deadline for a project and hit some issues with the tide/typescript tooling in my spacemacs and quickly switched over to VS Code with VSpaceCode [1]. I was actually pretty impressed with the setup and didn’t feel at all out of place. Having magit there was a welcome surprise. If there was an org-mode replacement I might even make the switch permanent, as much as I love spacemacs sometimes I just don’t want to fiddle with my configs so much.
So yes, thanks for making this, it saved me just the other week!
[1] I generally spend my time with Go/Rust, it was likely user error.
I'm still not sure if I have my Tide/Typescript set up properly in Emacs either - I think currently I have web-mode and a couple of other packages for formatting and linting, but I'm also rarely in that world these days.
Are/were you using one of the lsp-mode packages for Typescript?
edamagit for VSCode has evolved quite a bit since initially posting the alpha here. It's still in preview, but more magit and forge features are now present. Would love some more feedback, and pointers to areas to focus on. (Have had some contributions, but mostly it's me working on this)
Any tips on how to activate edamagit in VSCode? I have edamagit installed but I can't figure out how to actually open it to use it....dumb question-- I apologize-- but I've been struggling to find a clear answer on google :/
Yes, after installation you can use the default keyboard shortcut ‘Alt+x g’ to open the edamagit status view.
You could also run the command ‘Magit Status’ from the VSCode command pallete. [1]
For now Github is the only supported forge. The repo has to have a github remote defined, and it will try to load issues and pull requests.
The forge functionality is very new.
This is a very cool plugin! I'm the sole Emacs user on my team, who mostly use VS Code, and I'm always extolling the virtues of Magit. I can't wait to share this with them tomorrow!
I'm not sure, haven't tried.
Onivim2 looks cool! Looks like they support VSCode extensions, so hopefully it'll work without too much hassle.
For the VSCodeVim extensions I recommend alternative edamagit keybindings to avoid collisions. These are available in the edamagit README.md
As an Emacs and VSCodium user, that's an idea I hadn't thought of: replicating Emacs packages in VSCode/Codium. Nice. I'm curious how this compares to the out-of-the-box git integration in VSCode.
I used Atom for a year on a break from Vim. I got it working JUST like Vim but the biggest thing missing was a decent Git experience. I found a plugin that was a lot like Magit (the thing I liked most about Emacs). I used that until Atom got a good Git experience. Later I tried the same thing with VSCode. It's Vim-ish experience is just not as good. I'd love to go back and try it with this though. VSC's default Git experience leaves a LOT to be desired.
They have been improving the git plugin quite a bit in very recent times... adding a lot of functionality that was missing. I still go back to spacemacs when i needed to do more advanced workflows but the basic stuff in vscode is not bad anymore(though rebasing i am still way more comfortable in magit)
I am excited for this to be fleshed out and hope it's closer to a nice magit experience.
Yeah, definitely. With the way that editor improves month over month, I can imagine its Git support will be in a great place at some point. It's really nice that they'res so much steam behind development by Microsoft. I hated that Atom ran out of steam too soon.
I've heard a lot of love for the GitLens extension over the years. From what I could see, it doesn't help stage/and or commit though. It's mostly just data about branches/existing commits, right?
I have heard this. I really do like just plain old NeoVim. I tend to only mess with full blown IDE style editors just to have an idea what's available for other devs on my team. (I don't ever want to pressure someone to learn Vim/Emacs)
Right, and forget it if you think your Vim is somehow going to magically look like the beautiful screenshots you see on the Vim theme sites. Getting a terminal to properly handle 256 colors or more is annoying in and of itself. (definitely not impossible). It's nice to launch an editor, download some plugins, choose a theme and just GO.
I didn’t know about the forge features, will check those out.