Running OpenOffice from the Command Line on Mac OSX
August 12th, 2007
This is a simple hack to enable you to start OpenOffice and, more importantly, open documents with it from the command line. I’ve got the standard X port of OpenOffice 2.0 installed, so if you have something different you may need to change the path to soffice given below (to find soffice on your machine try from the command line $ locate soffice):
First let’s make the script that starts openoffice available in a convenient way e.g. by symlinking into ~/bin or /usr/bin:
$ cd ~/bin
$ ln -s /Applications/OpenOffice.org\ 2.0.app/Contents/openoffice.org/program/soffice ./
Now you can do stuff like:
$ soffice -help
You’ll see there are different switches which allow you to start a text document, a spreadsheet etc. One annoyance to note is that if you get soffice to load a file by doing:
$ soffice [options] ${filename}
The application it will use (writer, calc, math …) will depend solely on the extension of the filename and will ignore any options you give it. So e.g. if you do:
$ soffice -writer some.csv
Then this will load in calc even though the -writer option was given. For more details (on this very old bug) see:
http://www.openoffice.org/servlets/ReadMsg?list=allbugs&msgNo=94354
Fortunately this isn’t too much of a problem since the extension mapping is pretty reasonable.

August 12th, 2007 at 11:04 pm
Do you know that OpenOffice.org 2.2.1 is now available. Soon OpenOffice.org 2.3 will be available, it is currently in feature freeze state.
http://porting.openoffice.org/mac/download/x11-104.html
You will find the above issue appears to be already fixed see:
http://www.openoffice.org/issues/show_bug.cgi?id=18338
August 13th, 2007 at 9:44 am
Thanks for the comments Shaun and good to know there are newer versions available. I had looked for the issue in the tracker to see if it was resolved but had no luck so thanks for your links (I think the item directly dealing with what I mentioned is: http://www.openoffice.org/issues/show_bug.cgi?id=23327) .
What I do find odd is all of these issues were closed back in 2004 but I’m using OO 2.0 and I only downloaded it a year or so ago so I’m not sure why I still encounter it.