nerofair.blogg.se

#Gitx mac install
#Gitx mac code
#Gitx mac mac

#Gitx mac install

First we’re going to install the fantastic Homebrew, which is an easy way to install UNIX tools on your Mac.And it shows off some really cool tools-and no, sadly I’m not making money on any of them.) (Ok, you don’t need $10 to try Lisp, but this approach is bloody convenient. Next we’ll install Steel Bank Common Lisp (SBCL), a popular Lisp compiler / interpreter.To install Homebrew, open Terminal.app and paste in the following command : /usr/bin/ruby -e "$(curl -fsSL )" Now simply hit return and follow the prompts on screen ( additional details on installing Homebrew).

#Gitx mac mac

Install CodeRunner from the Mac App Store.Now that we have Homebrew it’s as easy as running brew install sbcl at the terminal.

#Gitx mac code

This step will cost you your hard-earned $10 but it’ll leave you with a fantastic little tool for quickly experimenting with snippets of code in a variety of different programming languages.

Once CodeRunner is finished installing, open it and hit ⌘, to open the Preferences window.

Switch to the Languages tab, add a new entry for Common Lisp, and configure it as shown:

Go! After closing the Preferences window, change the Language in the top left of the CodeRunner window to Common Lisp.A few of my Git tricks, tips and workflows.

Note: A german translation is available here This post is based on a talk I gave at the 18th Cocoaheads Meetup Vienna (CHW018) on Feb 17th, 2011. It is an annotated tour of my Git config, Git related scripts and commands, and various other tips and tricks I picked up over the years. You can find most of these things in my dotfiles repo, as well with a lot of other stuff, like parts of my Zsh config. Warning: Some of these tricks and tips are specific to my setup (Mac OS X Snow Leopard, Git 1.7.4) and workflow(s), and might not quite work for you as described. I also assume you have basic knowledge of the command line. No matter what you’re doing with Git, there’s always some kind of documentation that can help you out. There are basically two ways on the command line. The first one is typing git -h (replacing with the command in question of course), and Git will print a short overview of the call syntax as well as the most important options for you. The second one is having a look at the manpages themselves. The fastest way to get to them is by typing git help, and git will open them for you. They are more thorough, but aren’t for the faint of heart either. On the web, there are a few more options.

The Git Homepage lists quite a few introductions, tutorials, guides as well as online books that can help you out. I use Git primarily from the command line.

Luckily, enabling the Git completion for both Bash and Zsh is quite easy if you used Homebrew to install Git. Simply add the following to your ~/.bashrc: Gitx homebrew install#

Now, you’ll notice that for each and every git config I used the -global option. The reason for that is that Git not only looks at your global gitconfig (located at ~/.gitconfig), but also a repository-specific config (. So you can customize all these settings for each of your repository to your liking, just run the git config command in your repository without the -global flag. You don’t want to commit all your files into your repository. Things like temporary files, logs, configurations that are specific to a computer, files that are for testing only, private keys for code signing or files that can be easily regenerated all don’t belong in your repository. However, they will still show up whenever you type git status, even though they are purely noise at that point.įor this reason you can specify what files you want Git to ignore in a special file called.