Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Magit 3.0

emacsair.me

Post reply on HN
Print view View original

31–40 of 144 posts

Re: Magit 3.0

#31

Post by dreamcompiler »

mekster wrote: post #23

How does the interface compare to SourceTree?

Magit is designed for people who are already used to the git command line. Sourcetree is not.

Sourcetree is mouse-oriented, and to me it has the same disadvantages as all git GUI clients: I'm never quite sure what it's doing behind the scenes, and it cannot quite do everything useful that command line git can do.

Magit is keyboard-centric like emacs. Yes, so is the command line but Magit relies on individual keystrokes rather than typing in a line of commands and hitting . The result is that once you get used to Magit you can fly through git operations and it's almost always quite clear what git operations Magit is doing. There are still a few exotic command line git operations Magit won't do but I almost never need them.

Re: Magit 3.0

#33

Post by zelphirkalt »

Looking forward to using the new release. "git at the speed of thought" describes magit quite well. Actually sometimes magit nudged me into the direction of looking up some more special git commands, to learn about them and then making use of magit's interface to them, often simply pressing one button more. Magit has not made me forget how command line git works, because it often shows me right there, what the arguments are I am specifying by a few key presses actually are. If it made me forget how to use actual git, I would be thinking: "Meh, but I should know how to use git actually, for the times when I do not have magit around." Fortunately this is not the case at all with magit.

Re: Magit 3.0

#34

Post by Decabytes »

Magit is incredible and Emacs is my main Editor. Reading the post a couple days ago on text selection and how hard it is to get right makes me even more in awe of what a text editor does

Re: Magit 3.0

#35

Post by Decabytes »

Tehchops wrote: post #27
TacticalCoder wrote: post #20

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…

I'm using the Emacs Mac port on a modern(2019-era) MBP and it absolutely crawls when working on a large, multi-file Terraform code base.

Same. I have to work with large separated value files and it can get Emacs chugging on my Mac Book. Also any file large file that has any sort of highlighting (I.E a large xml file) can be difficult to work with.

I'm hoping that GCC emacs will resolve some of these issues. A better Elisp backend will do so much for Emacs and all of it's modes. I think one of Guilemacs goals was to have a better elisp interpreter but I'm not sure they will ever be able to keep up with all the development that has been happening on Emacs

Re: Magit 3.0

#36

Post by jorams »

warp wrote: post #19
pmoriarty wrote: post #9

Earlier quoted context omitted.

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.

> 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?

There are different styles available. While blaming a file, press B to open the popup, then c to cycle through them.

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

That's just the entire staging workflow. You see a list of changed files, which you can stage per file. Or you can expand a file to its changed chunks using TAB, then stage chunk by chunk. Or you can select some lines in the chunk and stage only those.

Re: Magit 3.0

#37

Post by Steltek »

zelphirkalt wrote: post #33

Looking forward to using the new release. "git at the speed of thought" describes magit quite well. Actually sometimes magit nudged me into the direction of looking up some more special git commands, to learn about them and then making use of magit's interface to them, often simply pressing one button more. Magit has not made me forget how command line git works, because it often shows me right there, what the argume…

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.

Re: Magit 3.0

#38

Post by darthrupert »

TacticalCoder wrote: post #20
the_duke wrote: 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…

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.

Re: Magit 3.0

#39

Post by 2pEXgD0fZ5cF »

chewxy wrote: post #26

I ran `magit-version` and I got Magit 20201225.4, which I assume is the 2020 Christmas edition of Magit. Did they suddenly switch to semver?

You are probably using melpa instead of melpa stable (like most, I assume). In melpa, all packages use the yyyymmdd.x type of versioning. In melpa stable packages use semver.

Have a look:

https://melpa.org/#/magit

https://stable.melpa.org/#/magit

Re: Magit 3.0

#40

Post by xvilka »

the_duke wrote: 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

They could have solved this with porting from single-threaded Emacs Lisp to Guile[1] or a proper Common Lisp[2]. Sadly, both initiatives didn't get enough steam. Someone, though, started to rewrite Climacs in SBCL from scratch[3].

[1] https://www.emacswiki.org/emacs/GuileEmacs

[2] https://www.cliki.net/cl-emacs

[3] https://github.com/robert-strandh/Second-Climacs

Post reply on HN