Blogmate is a bit easier on the eyes, it has (kind of) the same panel as ecto, which makes it easy to see what posts you have made so far. To write a new post, you just start typing and when you are done, press ‘Send Post’.

All of this is possible as well using the regular blogging-bundle. The plus of blogmate is the window with a list of your posts, the plus of the blogging-bundle is better headers when you download a post to edit. When I started with blogmate, and then wanted to edit the post with the blogging-bundle, the bundle got mixed up, and thought my blog was written in markup, while on wordpress.com you only can use html using xmlrpc, as far as I can tell.

Opinion: Both are nice plugins for textmate, and I will probably use blogmate for the nice list, and use the regular bundle for editing.

There are a whole list of public git servers out there, but I decided to go for http://repo.or.cz/ maintained by Petr Baudis. It has a basic web interface for creating or forking projects and was the first public Git hosting site (info from here, which has a whole list of public git servers).

To start using git you have to install it off course, on Debian/Ubuntu this can be done with a simple:

sudo apt-get install git-core

But there are packages for most common OSes here.

Setting up a repo on repo.or.cz

Ok, first we have to add ourselves as a user to repo.or.cz. For that we need to create an ssh-key, good tutorials are this one or this one.

Copy your public key, located in ~/.ssh/id_dsa.pub to http://repo.or.cz/m/reguser.cgi, fill out login and email information, and the first step is done.

Next, add a new project here (For example I used SimpleScripts). It will give a new repo like this: http://repo.or.cz/w/SimpleScripts.git.

fatal: no matching remote head

Now comes the weird part. Initially I had the idea to pull the repo, move my stuff into it, commit it and I would be done, but no, that is not how it works.

What will happen is this:

$ git clone ssh://repo.or.cz/srv/git/SimpleScripts.git
Initialized empty Git repository in /home/user/git/SimpleScripts/.git/
fatal: no matching remote head

Which is git’s way of saying the remote repo is empty. Right. Here I found the answer. It is actually quite logical, you want to push stuff you already have to the web, so you must start locally, and push that to your new repo.

$ git init #make a new repo, or use one you made earlier

Now we add some content:

$ touch README
$ git add README
$ git commit -a -m "First commit."

Next we have to edit the git config file:

$ $EDITOR .git/config

and add the following to the bottom:

[branch "master"]
remote = origin
merge = refs/heads/master

[remote "origin"] should be there already. Now we do:

$ git push origin master


This will push your content to remote and from now on pushing/pulling will
work as we expected.

I am happy Richard Jones figured all this out already Thanks!

Now I can add the wp-all script I did all this for. It is a small script to automate local wordpress installs to work on themes and play around. It pushes the ne wp install in git as well, so you can keep track of changes.

• Basic bilingual
  For now it only works for two languages.
• Language linker

This seems a bit of hack, usefull, but not so elegant. You just use two complete wordpress installs, and the one points to the other.

• Xili language plugin
  This looks like the correct way to make wordpress use more then one language. Every post has its own page and everything else gets translated as well.
• Language plugin

  So far this is the one I use. It is also a bit hackish, but very simple to use, all text is posted within the same post. It uses tags around entries to distinguish them. For an example see further down.

Installation and use of the poplarware plugin

Installation is straightforward, copy the plugin to the plugin directory, enabling the plugin and make several changes. The first is some sort of a language switcher, for example in the sidebar:

On pages or posts you use the following:


[lang_en]This is the post text in English[/lang_en]
[lang_es]Esto es el texto del artículo en español[/lang_es]
[lang_all]I want this text to appear for all languages[/lang_all]
This text that is not in a language tag will also appear for all languages.


For more examples and how to further make your side multilanguage, go here.

Introduction

OSX has several shells installed. Still, for people who want to do more with their computer the shell is important enough to warrant some extra effort. Zsh is the most powerfull shell available today. With very little investment in time, many things can be made a lot easier in the long run, using zsh. My favorite is being able to use tab-completion on a foreign host when I am using ssh, but there are many others.

The latest version of zsh plus the templates on google-code
will make working on the command-line on OSX fast and very effective.

Installation

Zsh is already installed on recent versions on OSX (try which zsh, probably /usr/bin/zsh), but the devel version on fink or ports is much more up-to-date.

I am using mac-ports (mac-ports guide), but fink works along the same lines:

sudo port install zsh-devel +mp_completion +pcre +dec +examples

Additional zsh templates: zsh-templates-osx on google-code, can be installed using:


cd /Library
sudo svn co http://zsh-templates-osx.googlecode.com/svn/trunk/Library/init
cd /private
sudo svn co http://zsh-templates-osx.googlecode.com/svn/trunk/etc


To get quickly up-to-speed install the files from /private/etc to ~/.zshrc and ~/.zshenv. When you run the zsh shell for the first time (after copying these files in place) it will ask you to configure the shell and in a couple of minutes you have a really nice shell.

Note: To make your rc files look half decent, set them to Shell Script, if you are using textmate, using: ⌃⌥⇧S – 1, or from the menu at the bottom of the edit-window

Files to store personal configuration (but see ~/.zsh):

• ~/.zsh/aliases.mine
• ~/.zsh/functions.mine

Goodies

Command-line-completion

So what makes zsh actually better then, say bash with command-line completion? Well, for starters, the command-line-completion , bash has caught on but not yet overtaken zsh. Take for example the port command:

# port ⇥

On pressing ⇥(tab) zsh will show you all the secondary commands port takes, pressing tab ones again, it will activate activate, now you can use tab or the arrow-keys to navigate to the command you need.

Ssh

A lot of administration work is done using ssh. OSX can make working with ssh a lot faster as well. The google templates have some extra tools as well, that will make it easier to configure what users and hosts actually get completed using ⇥. Configuration can be done using user_setup or host_setup.

To avoid being asked for ssh passwords all the time, install a shared key on the server you want to administer (see
here). Now when you, for example, try to copy a a file, you can use command-line-completion just as you can on a local host.

Note: Use SSHKeychain as an ssh-agent (sudo port install SSHKeychain)

More later…

Links

• Zsh template suite
• ZSH on OSX