Live data from Hacker News

Magit 3.0

emacsair.me

101–110 of 144 posts

Re: Magit 3.0

#101
post #5

I haven't tried very hard yet, but magic has been fairly unintuitive for me. Perhaps it's just that I've been using git for so long. There have been several times that I tried something with magit, and messed things up enough that I just dropped into a shell and did everything with the git command line

I've had the same experience. I've been using org-mode as my primary note-taking tool for several months now and am getting more comfortable with emacs as a result, but while I can see the appeal of magit, the "spend time learning how emacs git" vs "use the CLI to do what I want in 3 s" hasn't balanced out yet in magit's favor. At some point I'll probably sit down and take like a half day or so to actually learn magit, but git CLI isn't really broken for me so the drive to learn an alternative git tool hasn't been all that strong. Still, magit seems nice, so one of these days I'll probably make the effort.

Re: Magit 3.0

#102

Earlier quoted context omitted.

I was a longtime Emacs user (and vim before that) and recently a project I was working on was far too laggy for me to actually work productively on in Emacs. It was largely due to me using various LSPs within Emacs -- the frontend was in TypeScript and the backend in Go, and inevitably things would grind to a halt on a 5 year old i7 MBP with 16GB of RAM. Switched over to VSCode with as many extensions as I could find…

I have the exact same story. Multiple LSPs in emacs was too hard to manage and seeing as some of it was typescript, much worse than the VSCode experience. Edamagit has made a very good start at emulating magit in VSCode. Still use emacs for magit though.

It's probably too late for you :), but I use native-comp Emacs and it's blazing fast. At least lsp-mode+gopls is. I haven't gotten the chance to use this setup with Typescript's LS, but I've used gopls+clangd without slow downs.

Also, dang I miss coding in TS instead of Go.

Re: Magit 3.0

#103

Magit must be one of the best software tools ever written. I sorely missed it when I had to use IntelliJ for a few projects, so I wrote a TUI tool like Magit that can be used inside the console window of most IDEs like IntelliJ etc. Still haven't gotten around to releasing it properly, but it's easy to setup and works well enough to be a working MVP. https://github.com/hugit-project/hugit

You haven't touched its core code for two years, what happened? Gave it up?

Re: Magit 3.0

#104
post #5

I haven't tried very hard yet, but magic has been fairly unintuitive for me. Perhaps it's just that I've been using git for so long. There have been several times that I tried something with magit, and messed things up enough that I just dropped into a shell and did everything with the git command line

I've had the same experience. I've been using org-mode as my primary note-taking tool for several months now and am getting more comfortable with emacs as a result, but while I can see the appeal of magit, the "spend time learning how emacs git" vs "use the CLI to do what I want in 3 s" hasn't balanced out yet in magit's favor. At some point I'll probably sit down and take like a half day or so to actually learn magi…

How often do you guys do really crazy stuff with git? I do some rebasing (interactively and not) and some cherry picking, very rarely do I touch reflog (in which case I do use the CLI).

What kind of race car stuff does git CLI offer that makes you have to go through weird contortions in magit :)?

Re: Magit 3.0

#105
I wish Git would have some kind of command-server mode or libgit2 was supported with Magit to prevent needing to create new processes on Windows. Magit sometimes creates dozens of Git processes for a single operation, but because process creation is much slower on Windows than Linux, it makes Magit unusable for me on those systems. (Sadly, I don't always get a choice to just use Linux.) Simple things like magit-status take 10 seconds per refresh/stage/unstage instead of half a second elsewhere. It got to the point where using the git command line was much more bearable, but way more error-prone, and I miss Magit every time.

https://magit.vc/manual/magit/Microsoft-Windows-Performance....

https://github.com/magit/magit/issues/2959

Re: Magit 3.0

#106

Earlier quoted context omitted.

I upvoted you but... How comes Emacs is laggy for you? I'm running a beefy Emacs setup and it is really responsive. If anything Emacs in the nineties was "Eight Megabytes And Constantly Swapping" but... We're in 2021 now and now it's still 8 MB, so it's a rounding error (I'm only exaggerating a bit). It's one my lightest app: starting Emacs, eval'ing some elisp, and exiting takes... 81 ms. Eighty-one milliseconds. To…

Perhaps this is about MacOS vs Linux. I'm also suffering from slow emacs on mac, and no combination of flags seems to help. Use case: open a yaml file with syntax highlightning, scroll it with the mouse. The latency should be as low as possible.

I have a very underpowered Macos machine (2010 Mac mini) which faces latency problems with most things. Except Emacs. E.g., Eshell is much snappier for issuing shell commands than bash on iTerm2.

Re: Magit 3.0

#107

Earlier quoted context omitted.

I've had the same experience. I've been using org-mode as my primary note-taking tool for several months now and am getting more comfortable with emacs as a result, but while I can see the appeal of magit, the "spend time learning how emacs git" vs "use the CLI to do what I want in 3 s" hasn't balanced out yet in magit's favor. At some point I'll probably sit down and take like a half day or so to actually learn magi…

How often do you guys do really crazy stuff with git? I do some rebasing (interactively and not) and some cherry picking, very rarely do I touch reflog (in which case I do use the CLI). What kind of race car stuff does git CLI offer that makes you have to go through weird contortions in magit :)?

Well to use magit, first it's "ah, how do I open magit again?" Then it's "crap, now my org-mode buffer has been replaced by magit when I really wanted it in a separate tab but forgot to do the right key combo for that", then 5 minutes of googling "how to go back to previous screen in emacs doom", then remembering it's called a "buffer" That kind of stuff. I still get thrown off a surprising number of time by fat-fingering something and my emacs doing something surprising that I don't understand and am not sure what keys I touched to make it do that, and being unable to go back easily.

So it's really 100% on me for not being an emacs native rather than any shortcoming of magit per se, and as I said at some point I'll probably invest the time, but I _already_ have muscle memory for working in my terminal.

Re: Magit 3.0

#108

Earlier quoted context omitted.

I have the exact same story. Multiple LSPs in emacs was too hard to manage and seeing as some of it was typescript, much worse than the VSCode experience. Edamagit has made a very good start at emulating magit in VSCode. Still use emacs for magit though.

It's probably too late for you :), but I use native-comp Emacs and it's blazing fast. At least lsp-mode+gopls is. I haven't gotten the chance to use this setup with Typescript's LS, but I've used gopls+clangd without slow downs. Also, dang I miss coding in TS instead of Go.

I have the same experience. Being on master and nativecomp probably helps, and I also think eglot is tad smoother than lsp-mode. I am using 10 year old laptop, no friction at all with tsserver, elixir-ls or gopls. However I think the server itself is the biggest difference maker, because all hell breaks lose when I try dart/flutter even in a simple project. But to be fair, my neovim setup struggles with that too (nvim-lspconfig + nvim-compe).

Re: Magit 3.0

#109
post #37

Earlier quoted context omitted.

Magit has a great mix of direct manipulation of git primitives and good visualization. I think I've learned how git works faster through Magit than I would have from using the CLI. It's really hit a sweet spot for me.

This is what I'd want from any GUI, ability to "view source" and then use in scripting etc.

I'm sure you know this, but for the benefit of other readers, pressing '$' in Magit status buffer (and likely bunch of others) pops up a buffer that lists actual commands issued to Git, so you can always check how Magit interaction maps to Git CLI commands.

Re: Magit 3.0

#110
post #88
post #6

Emacs is too laggy for me as my main editor. But Magit is so good that I start emacs up just to use it as my Git interface if I can't get by just with the CLI. Sadly there is no Vim plugin that is competitive. There is vimagit [1], but it's not on par. [1] https://github.com/jreybert/vimagit

I agree. At work we use Windows and all the dev tools are integrated to Emacs (and Emacs alone). And magit is just incredibly slow.

I had some performance issues with Magit (and git in general) under Windows, but ultimately resolved them. I documented the solutions here: https://news.ycombinator.com/item?id=26736006. Maybe some of it will work for your case.
Post reply on HN