Code That Matters » henke

Git autocomplete in Mac OS X

henke — Fri, 08 Jan 2010 08:23:32 +0000

I always liked that my Git installations on Unix and Linux comes with the contrib/complete/git-completion.bash script activated or easily activated. But its harder if you use the pre-built binaries for Mac OS X.

To get autocompletion to work on Mac OS X when installing the pre-built binaries do this.
UPDATE: Instead of step 1 and 2 below you can get the completion script directly from Github. Thanks to Fredric.

curl http://github.com/git/git/raw/master/contrib/completion/git-completion.bash -O

UPDATE: 2011-01-03 All github.com url are now https. Thanks to Julio.

curl https://github.com/git/git/raw/master/contrib/completion/git-completion.bash -O

UPDATE: 2011-07-15 Added -L option to allow for curl to handle redirects.Thanks to michaelyoung.

curl https://github.com/git/git/raw/master/contrib/completion/git-completion.bash -OL

1. Download the Git source from git-scm.com.
2. Unpack and copy the completion script git-completion.bash found in contrib/completion to your home directory.

3. Add the following to your ~/.profile or ~/.bash_profile

source ~/git-completion.bash
 
alias gco='git co'
alias gci='git ci'
alias grb='git rb'

4. Add the following to your ~/.gitconfig

[alias]
co = checkout
ci = commit
rb = rebase

Restart Terminal and start Tabbin’!

More Git tips that I found usefull can be found on Tim Dysinger’s blog http://dysinger.net/2007/12/30/installing-git-on-mac-os-x-105-leopard

Redirect to previous url after delete

henke — Fri, 02 Oct 2009 14:03:31 +0000

Ever wondered how you can easily redirect a user to the previous url? I.e after a users clicks a delete link or some other action you can use the more common url.current() because that points to the delete action. Instead use request.header REFERER like this:
UPDATE: New way of doing this in pylons 1.0 as redirect_to is replaced by redirect. Thanks to DB for pointing that out!

(This is a Pylons example)

redirect(url(request.referer))

Done!

Unicode in Mako using Pylons

henke — Fri, 02 Oct 2009 07:18:02 +0000

Small post regarding unicode support in mako. I learned yesterday that mako not only has input and output encoding options but also an default_filter encoding. In the environment.py file, in your Pylons config folder, you need all these three to be sure that everything is enoded as unicode. Remember though that the default_filters argument can have big impact on performance.

(If someone knows the configuration files for other frameworks, please write a comment about it and I’ll add it to the post)

Please read the Mako unicode chapter here if you want the gory details.

#environment.py
 config['pylons.app_globals'].mako_lookup = TemplateLookup(
        input_encoding='utf-8', 
        output_encoding='utf-8', 
        default_filters=['decode.utf8'] )

Serving images directly from database

henke — Thu, 01 Oct 2009 08:54:13 +0000

Even though storing images in the database have its advantages/disadvantages, here is a small guide for those who want to store them in the database and serve them directly to the browser without having to generate a file first. This examples is based on the amazing web framework pylons.

In this example I want to serve small product images from my product controller.

In the product.py controller I have this method

def show_image(self, id, name):
    response.headers['Content-type'] = 'image/png'
    response.headers['Cache-Control'] = 'max-age=14400'
    response.headers['Pragma'] = ''
    product = Product.get_by(id=id)
    return product.image

Then in my mako template I have

 src="url(controller='product', action='show_image', id='${c.product.id}', name='c.product.image_name')"/>

which will generate

 src="/product/show_image/1/super-glue.png"/>

So whats happening is that when the page is loading the image tag, the show_image() function is called which fetches the image data from the database and returns the image data buffer to the template. The key for this to work is to set the appropriate headers so that the page know that the data returned is image/png through the Content-type. The name argument is just used to set a name for the image file on the connecting client so that the cached file will have a correct name.