3 ms·
I've been a vim user for so long it doesn't even make sense to do the math to give a year. Around 2013, my buddy at work and I switched to Emacs just to try som
by nobleach 3y ago
I've been a vim user for so long it doesn't even make sense to do the math to give a year. Around 2013, my buddy at work and I switched to Emacs just to try something different. We only lasted a few months. One thing that I took away from that experience was Magit. I was a CLI user of Git because all the other interfaces just bothered me. When I went back to Vim, I started using fugitive. It wasn't bad, but it just didn't have that same Magit feel that I really enjoyed. I tried the Atom text editor for about a year. It was the best Vim-emulator I'd ever seen at the time. Someone had been working on a Magit clone for it. It reminded me of how enjoyable Magit truly was. Flash forward a couple of years, I'm on NeoVim and someone starts working on NeoGit. I couldn't contain my excitement. It's cool to see someone untangle the experience from any one particular editor.
- myaccountonhn 3y agoHave you tried tig? Ultimately I’ve started using that instead and it works great as a magit replacement. I use it together with Kakoune in daemon mode, so I can jump in and out of files with tig and have the state with buffers remain.
- okl 3y agotig is great. One of my favourite features is that you can define your own shortcuts in the global .gitconfig. For example, when I press `=` it creates a fixup commit for the selected commit. That, together with the ability to stage single lines completely changed my workflow. Recently, I have become a bit lazy and use PyCharm to stage and commit changes. Its diff viewer also supports staging single lines but its better integrated. For example, pressing F4 jumps to the current file/line in the main window.
- timeforcomputer 3y agoI love tig. I have an ad-hoc fork of it adding a new window which displays a preview of the selected file in the diff prelude section of the diff window, so I don't have to navigate through the single window. It is very helpful to browse the files in a diff easily. (https://github.com/LucasPayne/tig https://github.com/LucasPayne/tig) I swear I will clean up the fork soon, I just implemented it in whatever way worked. I do something similar to what you are doing with Kakoune daemon mode, but I work in the shell within a vim context. I have bound "e" in diff/stage views of tig to send a message to the current vim to open a new tab for that file at that line. I have not tried magit yet but am going to now to at least extract some great ideas from it and somehow get it in my current workflow.
- nobleach 3y agoI haven't. I've only heard of it. For a very short period of time I tried to get into LazyGit running in my Vim terminal. I just couldn't make the workflow work for me. You know how it is when it gets into muscle memory, and you really begin to fly? Yeah, LazyGit didn't ever happen. (Not LazyGit's fault obviously). I may try to play with tig as I'm always looking at different tools. Occasionally I even run into game-changers when trying these things.
- robenkleene 3y agoLazyGit (and gitui), don't use use the `EDITOR` environment variable to delegate to the editor (e.g., Vim). So the Magit-like workflow (where you freely jump to hunks to edit them and then return to the status view) isn't possible in them. Tig is the only well-known git TUI that does this, making it the only git TUI that works smoothly with Vim.
- funcDropShadow 3y agoHave you tried magit with making it use $EDITOR for commit messages?
- nobleach 3y agoI haven't used magit in so many years. Wow...I don't have emacs installed on this machine! (I still keep my configs in my dotfiles though)