vscode-gitlens VS vscode-emacs-mcx

Quite a while ago, the GitLens+ plugin gained the Commit Graph feature--the same graph you see in GitKraken. Until then I had used Git Graph for visualizing my repositories and GitLens+ for git blame in the GUI. Since one plugin could now do both, the natural course of action was to remove the other--goodbye, Git Graph!

Btw, today I want to speak about something different, I love git and I love terminal, but sometimes I love having the info visualised appealingly and get info about the source control quickly. I work with VsCode typically, so some months ago I tried to find a solution for this editor that resolves what was said before. After googling and some testing, the result of my search was: GitLens. Now, I want to show you how it works and how it can improve your routine. So don't waste time and let's jump in it!

GitLens extension chef's kiss

for GitLens https://gitlens.amod.io/

Hi. Vs code is pretty well integrated with git. There are built in git support and a couple other plugins. For example, the most popular git plugin for vs code is git lens. It also has powerful rebase editor (i guess, it is my favorite feature), which you can enable by following this guide. I personally realy enjoing Git Graph extension, which allow you to observe your git history in pretty similar to git kraken way. It also provide navigation facilities and some other useful features.

Redder color means changes were made very recently in that area. Again you can fully customize age thresholds, locations, the color of the most recent and least recent changes, etc., from the settings.

So here are some of my favorite GitLens features that I use regularly. You can find the full list of the features here.

Phone a friend. I recommend integrating git blame into your development environment I use the Git lens plugin which shows you, directly within files in a code editor, who authored certain file changes and the PR which can be helpful for quickly getting more context regarding decisions by looking at the associated Pull Request or having the opportunity to connect directly with the committer. Pair programming can be an effective way to debug and share knowledge. Similar, to the magic of figuring out the solution to a bug in the shower or overnight there is a phenomenon called rubber ducky debugging in which just explaining the issue to someone else (even an inanimate rubber duck) can help make the solution more obvious.

If you're using VS Code, get the GitLens extension. It has an interactive rebase editor which I find very helpful (as well as heaps of other nice features).

GitLens - https://gitlens.amod.io/#features , see who did what, when and why in your IDE and also quickly see any changes you have made

Hi Mickey, ah no -- you've done WAY more than me in this area! I had been meaning to try your combobulate package.

FWIW: after 20 years of Emacs I personally switched to VSCode a couple of years ago because I felt that in Emacs I was missing out on the LSP experience that VSCode provided in Rust, Typescript, Scala, etc. (I was using Eglot). In any case, there's a very nice Emacs emulation mode in VSCode

https://github.com/whitphx/vscode-emacs-mcx

which includes some paredit functionality courtesy of

https://robert.kra.hn/past-projects/paredit-js.html

and I'm working on porting my favorite paredit function, paredit-kill. Unfortunately that's the one where the paredit author left this comment in the code:

  ;;; Please do not try to understand this code unless you have a VERY

It has been requested in the issue, but not been implemented yet; https://github.com/whitphx/vscode-emacs-mcx/issues/772

Yes. You can configure key assignments through keybindings.json. See https://code.visualstudio.com/docs/getstarted/keybindings#\_advanced-customization Combining multi commands are also possible with multi-command extension. These are examples. https://github.com/whitphx/vscode-emacs-mcx/issues/392 https://github.com/whitphx/vscode-emacs-mcx/issues/965