#Magit for aquamacs pdf#

A lot of the time 'Write programs that do one thing and do it well' really means 'I don't understand the difference between a procedure and a program.' It is much easier to write procedures than it is to write programs, and it is often easier to turn a procedure into a program than vice-versa ( emacsclient does the former especially well). Emacs falls down with images and navigating modern webpages though (haha modern anything written in my lifetime), so I use a browser like everyone else. Eg, at the moment I'm writing a comment for a website - if I only viewed sites like Hacker News (mostly text reading and editing) then I would 100% end up doing it from emacs. The secret is that many tasks involve 60% editing text and it then starts to make sense to implement the 40% in an environment where your heavily customised keyboard shortcuts all work. I must admit, the advantages aren't really there for me on this one, I prefer stand alone viewers.

#Magit for aquamacs pdf#

Has me stumped, although sometimes when I write documents that are going to be emailed as a pdf I'll use emacs and it makes a lot of sense to preview in place as I go.

I can see a lot of utility in a stand-alone calendar program if the workflow you want isn't based on text, though. If this is your workflow, again it makes more sense to implement from a text editor (because the 'calendar' is really a parsed text file and maintaining the text file is what the user works on). This one is pretty workflow sensitive, but Org Mode encourages a very holistic approach of writing everything related to a project in one file, then parsing the file for dates and creating a calendar. Especially for mostly-text emails or emails discussing, say, code. From this perspective, a text editor implementing email makes a lot more sense than an email client implementing text editing. My Magit split screen command.One view of email is really reading and composing lightly formatted text with a 'send' option. The function will result in following screen:Īs with all my Emacs commands, I've created a shortcut for the magit-split: (global-set-key (kbd 'C-x C-g') 'magit-split)

Balance the windows, so they have the same width.

Execute magit-status for the last repo.

Repeat step 1 with another repo as an argument.

Execute magit-status command for the path that is given as an argument.

So I put together a simple function that opens Magit for the three repositories I needed in a split screen: (defun magit-split () One of those were to have an easy way for opening Magit for several repositories in split screen. However, I quickly found a few things I needed to improve to make it perfect for my environment. I was really impressed with Magit and started to use it as my main tool for working with Git. I'm not going to explain how Magit works in this post, so if you're interested in learning more about Magit, take a look at the Magit repository and this great introduction by the Mastering Emacs blog. Magit is a great interface for Git in Emacs, which lets you work efficiently and with great control. A couple of months ago I started using Magit.