9 ms·

I started using magit about 3 months ago - it's definitely one of my favorite parts of emacs now. I highly recommend it to anyone using emacs as a daily driver.

by ddavis 8y ago

walkingolof 8y ago
Org-Mode being other other for me, its those two Emacs modules I use frequently, the rest have (for me) been superseded by other tools.
- mitchty 8y ago
  Org-mode, magit, and tramp are the three stools in emacs I keep resting on daily. Really is nothing quite like the trio of the tools.
  - AlexCoventry 8y ago
    REPL integration for python, clojure, etc. is a huge win, too.
    - dman 8y ago
      Ivy is the other thing that keeps making me come back to emacs.
      - globuous 8y ago
        I haven't tried ivy yet, got hot damn i love helm !!! I use it everywhere :p and actually, I recently fell in love with dired, I literally use it all the time. I like it better than finder or the command line !!
agumonkey 8y ago
how would you compare it to other git interfaces ? unless you used to use the bare git program in a shell.
- branchless 8y ago
  It's far superior to the intellij integration as they have a generic "version control". Magit is just so easy to use for discarding hunks / rebasing / etc. Quick, visually clear. I sometimes use emacs just to use magit when working with java on a fiddly git task even when I'm working in intellij to modify the actual code.
  - agumonkey 8y ago
    this should be sent to the magit team (even if its mostly Jonas these days I believe)
    - btschaegg 8y ago
      I think at least Jonas is aware of users like that -- there were some discussions on that concept during his Magit Kickstarter campaign[1]: > Make Magit more accessible to non-Emacs users > I think that Magit can be an excellent Git interface for users of other editors and IDEs. It would be a shame if its user-base continued to be limited to people who use Emacs for editing purposes. > To appeal to non-Emacs users, Magit has to be made more accessible. Additionally I intend to provide simplified Emacs configurations and documentation that teaches just enough Emacs to be able to use Magit. See Magit for users of other editors for more information. [1]: https://www.kickstarter.com/projects/1681258897/its-magit-the-magical-git-client https://www.kickstarter.com/projects/1681258897/its-magit-th...
- masklinn 8y ago
  It's the best git client I've used, comparing to git (CLI & gitk), PyCharm's builtin (even with the recent improvements e.g. hunkwise selection), tig, Sourcetree, gitx (various forks) and gitextensions. The rebase and interactive stage/unstage are especially stellar. It does get a tad slow on huge repositories, but that's the case of most git clients. Despite using pycharm for $dayjob, most of my interactions with git are through magit. Basically the only ones which are not are annotations-browsing (IDE integration is too convenient there) and branch-switching ($dayjob repo being huge, switching major branches can take some time and magit completely locks up emacs + has no feedback, so CLI is more convenient)
fsimon 8y ago
My favorite feature in magit is the ease of doing block and line level staging of hunks. It's normal in my workflow to touch on code unrelated to what I'm working on, fixing a typo here, a formatting fix there, refactoring or simplifying a statement that was unclear at first glance. Staging those changes and commiting them right away if there are more working on the code base or simply staging them as a separate commits when the current task done makes it so much easier to keep a clean history - without having to do intermediary commits or stashing. The feature is called git add --patch[0] in command line git but magit makes it so much more accessible. [0] https://git-scm.com/docs/git-add#git-add--p https://git-scm.com/docs/git-add#git-add--p
- masklinn 8y ago
  > My favorite feature in magit is the ease of doing block and line level staging of hunks. Doing so is also easy using command-line git (add -p, commit -p and hunkwise reverts with checkout -p), the great thing about magit is it lets me do so: 1. with a bird's eye view, git's <x> -p shows hunks independent from one another and asks me what I want to do, sometimes I have no idea because I don't really remember what the context of that change is (or if there is one) 2. nonlinearly, similarly to above git's <x> -p goes through each hunk one by one, in magit I can go back and forth in the diff buffer if I need more info, there are shortcuts to process it linearly but it's a help (because that's a common case) not a limitation of the tool

I started using magit about 3 months ago - it's definitely one of my favorite parts of emacs now. I highly recommend it to anyone using emacs as a daily driver.

by ddavis 8y ago

I started using magit about 3 months ago - it's definitely one of my favorite parts of emacs now. I highly recommend it to anyone using emacs as a daily driver.

walkingolof 8y ago

Org-Mode being other other for me, its those two Emacs modules I use frequently, the rest have (for me) been superseded by other tools.

mitchty 8y ago
Org-mode, magit, and tramp are the three stools in emacs I keep resting on daily. Really is nothing quite like the trio of the tools.
- AlexCoventry 8y ago
  REPL integration for python, clojure, etc. is a huge win, too.
  - dman 8y ago
    Ivy is the other thing that keeps making me come back to emacs.
    - globuous 8y ago
      I haven't tried ivy yet, got hot damn i love helm !!! I use it everywhere :p and actually, I recently fell in love with dired, I literally use it all the time. I like it better than finder or the command line !!

agumonkey 8y ago

how would you compare it to other git interfaces ? unless you used to use the bare git program in a shell.

branchless 8y ago
It's far superior to the intellij integration as they have a generic "version control". Magit is just so easy to use for discarding hunks / rebasing / etc. Quick, visually clear. I sometimes use emacs just to use magit when working with java on a fiddly git task even when I'm working in intellij to modify the actual code.
- agumonkey 8y ago
  this should be sent to the magit team (even if its mostly Jonas these days I believe)
  - btschaegg 8y ago
    I think at least Jonas is aware of users like that -- there were some discussions on that concept during his Magit Kickstarter campaign[1]: > Make Magit more accessible to non-Emacs users > I think that Magit can be an excellent Git interface for users of other editors and IDEs. It would be a shame if its user-base continued to be limited to people who use Emacs for editing purposes. > To appeal to non-Emacs users, Magit has to be made more accessible. Additionally I intend to provide simplified Emacs configurations and documentation that teaches just enough Emacs to be able to use Magit. See Magit for users of other editors for more information. [1]: https://www.kickstarter.com/projects/1681258897/its-magit-the-magical-git-client https://www.kickstarter.com/projects/1681258897/its-magit-th...
masklinn 8y ago
It's the best git client I've used, comparing to git (CLI & gitk), PyCharm's builtin (even with the recent improvements e.g. hunkwise selection), tig, Sourcetree, gitx (various forks) and gitextensions. The rebase and interactive stage/unstage are especially stellar. It does get a tad slow on huge repositories, but that's the case of most git clients. Despite using pycharm for $dayjob, most of my interactions with git are through magit. Basically the only ones which are not are annotations-browsing (IDE integration is too convenient there) and branch-switching ($dayjob repo being huge, switching major branches can take some time and magit completely locks up emacs + has no feedback, so CLI is more convenient)

fsimon 8y ago

My favorite feature in magit is the ease of doing block and line level staging of hunks. It's normal in my workflow to touch on code unrelated to what I'm working on, fixing a typo here, a formatting fix there, refactoring or simplifying a statement that was unclear at first glance. Staging those changes and commiting them right away if there are more working on the code base or simply staging them as a separate commits when the current task done makes it so much easier to keep a clean history - without having to do intermediary commits or stashing. The feature is called git add --patch[0] in command line git but magit makes it so much more accessible. [0] https://git-scm.com/docs/git-add#git-add--p https://git-scm.com/docs/git-add#git-add--p

masklinn 8y ago
> My favorite feature in magit is the ease of doing block and line level staging of hunks. Doing so is also easy using command-line git (add -p, commit -p and hunkwise reverts with checkout -p), the great thing about magit is it lets me do so: 1. with a bird's eye view, git's <x> -p shows hunks independent from one another and asks me what I want to do, sometimes I have no idea because I don't really remember what the context of that change is (or if there is one) 2. nonlinearly, similarly to above git's <x> -p goes through each hunk one by one, in magit I can go back and forth in the diff buffer if I need more info, there are shortcuts to process it linearly but it's a help (because that's a common case) not a limitation of the tool