Magit does more than make it possible to use the commands that youĪlready know more quickly than on the command line. Magit enables even advanced Git users to perform nearly all of theirĭaily version control tasks with a fraction of the effort that wouldīe required on the command line, without having to drop to thatĬommand line for “edge cases” as would be necessary with many other Than the relative completeness at any given time is that support forĪll of Git features could be added to Magit without any changes to its Interfaces are stuck somewhere around 60%. If I had to put a number on it, I would say that Magit supports aboutĩ0% of what can be done using git, while other third-party Interface concepts whenever possible, is more important than trying to Supported features into the interface, by taking advantage of Magit’s The reason that there still exist some gaps is that fully integrating That are supported are also improved upon. Only mean that it supports most Git features - most features Magit is essentially completeīy now, Magit is an essentially complete Git interface. Itself can do) want to perform on some visible (or invisible) thingĪctually is available, using only a single or very few mnemonic key Furthermore, unlike in GUI interfaces,Įvery action you might reasonably (based on your knowledge of what Git And most importantly everything thatĬan be seen is actionable. Instead all status information is automatically kept up-to-date and It is worth repeating that theĬrucial difference between Git and Magit is that Magit’s output is not Magit looks quite similar to the Git command line, prettier maybe, but Important of these concepts in more detail. Only) some innovative approach, but the fact that these concepts areĪpplied very consistently across all features. What makes their application in Magit powerful isn’t necessarily (or Magit heavily relies on a few simple, yet powerful interface concepts. What separates Magit from other Git interfaces? That, with a little practice, is both faster and more intuitive thanĮither the command line or a GUI. Interactive nature of a GUI, while not limiting the availability ofįeatures to certain specialized views. So one could say that Magit combines the completeness of Git with the In Magit, on the other hand, you can do virtuallyĮverything with some object that can be done with objects of that type That GUIs do expose tend to only by available in some view or dialogīut not another, even though the object that the feature would act on Magit is an essentially complete interface. Much further than just looks and input methods.Ĭurrent GUIs only expose a limited subset of Git’s features, while But the differences between Magit and Git GUIs go Of course in a GUI you would normallyĬlick on something to act on it, while Magit is primarily 1 driven Git GUIs are similar to Magit in that many things you can see in a GUIĬan also be acted on directly. Many commands act on the thing the cursor is on,Įither by showing more detailed or alternative information about it inĪ separate buffer or by performing an action with side-effects on it. CommandsĪre invoked, not by typing them out, but by pressing short mnemonic The status buffer, or any other Magit buffer, is actionable. Unlike the read-only output of git, everything that you can see in The mainĮntry point to Magit isn’t the command-line but its status buffer, User does not execute commands by typing them into a shell. Magit is a text-based user interface to Git. Emacsair! Magit, the magical Git interface About Posts Rss Twitter Github macsAir Collecting frequent-committer miles Magit, the magical Git interface Basic similarities and differences to other interfaces

Magit for aquamacs