Live data from Hacker News

Magit 3.0

emacsair.me

11–20 of 144 posts

Re: Magit 3.0

#11
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

Likewise with VSCode, Edamagit is very close but isn't "muscle memory" close. I run into things that aren't quite the same as the original: choosing a remote on a new repository when pushing or selecting switches using the VSCode native pop-up.

I really want Edamagit to work. I'm still getting my feet wet with VSCode but Git integration is a bit of a pain.

Re: Magit 3.0

#13
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.

I've been considering trying to replicate magit in a tui. I'm not sure if I should go for a straight port (many people might find useful, eventually) or change lots of things to make it fit my workflow (might be more likely to "finish" if I optimized for me).

My dream git workflow is rebase-first, i.e. you have multiple WIP commits at any given time, and can send an unstaged hunk to any of them with the same level of complexity.

Re: Magit 3.0

#14
post #4

I heard lots of praise to Magit. Is there a way to use it like a standalone git client? Like tig, lazygit, etc.

Sure, just open the git repo in a magit. I do it almost every day.

Re: Magit 3.0

#15
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

Do you remember what you tried? Yours has been literally the first negative comment out of hundreds of comments I've read about magit. It'd be interesting to learn what didn't work for you and why.

Cherry pick is faster and easier for me in the CLI. I’ve read Magit’s documentation on Cherry pick dozens of times and I still have no idea what it’s doing. I think I have successfully done it in magit once, but now I don’t bother and just do it on the command line.

For everything else I absolutely love magit. The ability to stage and commit chunks in a visual fashion is an unbeatable killer feature!

Re: Magit 3.0

#16
Magit hits the sweet spot between flexible and easy that makes it an actually useful git editor integration. You still need to know git to use it, though!

Re: Magit 3.0

#17
post #7
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

Tried native-comp? https://news.ycombinator.com/item?id=24117853

I have, on macOS, and somehow, it has much much worse lag than Mitsuharu Yamamoto's Emacs "Mac port," [1] which is still based on Emacs 27.2. The native comp version was so slow that I gave up and switched back to Mitsuharu's port, which is snappy enough for my needs even without the native compilation bits.

From what I gather, mainline Emacs was adversely impacted by changes in Mojave. [2][3] The end result, for me, is that any gains in the native compilation are swamped by the macOS issues. I'm hoping that Mistuharu rebases his work on the native-comp Emacs soon, so that I can get the best of both.

[1] https://bitbucket.org/mituharu/emacs-mac/src/master/

[2] https://www.reddit.com/r/emacs/comments/faz1fm/seeing_a_flas...

[3] https://emacs.stackexchange.com/questions/59966/is-it-possib...

Re: Magit 3.0

#18
Congratulations to Jonas and the whole team! Magit is a joy to use and has made me feel supremely comfortable with advanced git work.

Re: Magit 3.0

#19
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

Do you remember what you tried? Yours has been literally the first negative comment out of hundreds of comments I've read about magit. It'd be interesting to learn what didn't work for you and why.

My experience is the same. Probably because I'm so used to git on the command-line already magit doesn't seem much benefit.

I just gave it a try:

magit-blame seems hard to read, I guess it's a limitation of emacs, or can it be configured to show the author name on the left of the line like CLI git blame?

I tried to find the equivalent of "git add --patch", but did not find it in the info manual.

Re: Magit 3.0

#20
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 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 start an entire Emacs instance from scratch (no "daemon" trickery: a real full Emacs instance), eval'ing "kill emacs" (ok, a small program if any bu still) and exiting.

I don't know which editor, in this day and age, can start and exit in 81 ms (besides vim and nano)?

Launching my full setup takes 1.1s: thousands of lines of elisp configuration.

I'm running the native-comp branch since six months (?): compilation of Emacs itself is a bit of a pain but running it is very smooth.

That's on a 6 or 7 years old Core i7 6700K / 16 GB of RAM. Hardly a speed demon (besides the NVMe M.2 PCIe 3.0 x4 SSD).

Configuration, IIRC, has got a few "tricks" to prevent the usual culprits from slowing Emacs: something to do probably with font-locking on very long lines (?) when I open such a file etc.

But it's overall more than snappy. I use ivy/avy/swiper and burntsushi's rigpgrep integrated into Emacs. Everything is not just fast but really fast.

I cannot even imagine on a modern machine like some AMD 5900X or Apple M1...

Post reply on HN