TextMate is a great Mac OS X plain text editor with many features and supported coding languages. LaTeX support (syntax highlighting, commands, code snippets, etc.) in TextMate is provided by the LaTeX Bundle, that is contained in any TextMate installation by default.

LaTeX bundle defines a default shortcut Command+R to show a typesetting status dialog window with some buttons for additional actions – compiling bibliography, building index, previewing, etc. I wanted to have an additional action button to run MetaPost on the file with .mp extension:

To get the desired functionality, LaTeX bundle should be checked out from TextMate SVN and patched. Save the patch Latex.tmbundle.diff (file contents is listed below) to your Desktop and run the following commands in the Terminal:

$ cd ~/Desktop
$ svn co http://svn.textmate.org/trunk/Bundles/Latex.tmbundle
$ patch -p1 -d Latex.tmbundle < Latex.tmbundle.diff

To install updated LaTeX bundle into TextMate, simply double-click patched Latex.tmbundle, press “Update” in the dialog window. “Bundle Editor” TextMate window will be displayed, you may just close it.

That’s all. Your modified Latex.tmbundle was moved to ~/Library/Application Support/TextMate/Pristine Copy/Bundles and installed.

Latex.tmbundle.diff

The patch below was tested with TextMate 1.5.8, Latex.tmbundle SVN revision 11795 and LaTeX and MetaPost from MacTeX-2008.

diff -Naur Latex.tmbundle/Support/bin/texMate.py Latex.modified.tmbundle/Support/bin/texMate.py
--- Latex.tmbundle/Support/bin/texMate.py	2009-10-30 18:25:23.000000000 +0200
+++ Latex.modified.tmbundle/Support/bin/texMate.py	2009-10-30 18:26:29.000000000 +0200
@@ -140,6 +140,29 @@
         stat = runObj.wait()
     return stat,fatal,error,warning

+def run_metapost(mpostfile=None,texfile=None,verbose=False):
+    """Determine targets and run the metapost command"""
+    # find all the mp files.
+    fatal,err,warn = 0,0,0
+    mpfiles = []
+    if texfile:
+        basename = texfile[:texfile.rfind('.')]
+    if mpostfile == None:
+        mpfiles = [f[:f.rfind('.mp')] for f in os.listdir('.') if re.search('\.mp$',f) > 0]
+    else:
+        mpfiles = [mpostfile]
+    for f in mpfiles:
+        print '<h4>Processing: %s </h4>' % f
+        runObj = Popen('mpost -interaction=nonstopmode -tex=latex '+shell_quote(f),
+                       shell=True,stdout=PIPE,stdin=PIPE,stderr=STDOUT,close_fds=True)
+        p = MetaPostParser(runObj.stdout,verbose)
+        f,e,w = p.parseStream()
+        fatal|=f
+        err+=e
+        warn+=w
+        stat = runObj.wait()
+    return stat,fatal,err,warn
+
 def findViewerPath(viewer,pdfFile,fileName):
     """Use the find_app command to ensure that the viewer is installed in the system
        For apps that support pdfsync search in pdf set up the command to go to the part of
@@ -572,6 +595,9 @@
     elif texCommand == 'index':
         texStatus, isFatal, numErrs, numWarns = run_makeindex(fileName)

+    elif texCommand == 'metapost':
+        texStatus, isFatal, numErrs, numWarns = run_metapost(texfile=fileName)
+
     elif texCommand == 'clean':
         texCommand = 'latexmk.pl -CA '
         runObj = Popen(texCommand,shell=True,stdout=PIPE,stdin=PIPE,stderr=STDOUT,close_fds=True)
@@ -661,6 +687,7 @@
         print '<input type="button" value="Re-Run %s" onclick="runLatex(); return false" />' % engine
         print '<input type="button" value="Run BibTeX" onclick="runBibtex(); return false" />'
         print '<input type="button" value="Run Makeindex" onclick="runMakeIndex(); return false" />'
+        print '<input type="button" value="Run MetaPost" onclick="runMetaPost(); return false" />'
         print '<input type="button" value="Clean up" onclick="runClean(); return false" />'
         if viewer == 'TextMate':
             pdfFile = fileNoSuffix+'.pdf'
diff -Naur Latex.tmbundle/Support/bin/texlib.js Latex.modified.tmbundle/Support/bin/texlib.js
--- Latex.tmbundle/Support/bin/texlib.js	2009-10-30 18:25:23.000000000 +0200
+++ Latex.modified.tmbundle/Support/bin/texlib.js	2009-10-30 18:26:29.000000000 +0200
@@ -49,6 +49,10 @@
     runCommand('index')
 };

+function runMetaPost(){
+    runCommand('metapost')
+};
+
 function runView(){
     runCommand('view')
 };
diff -Naur Latex.tmbundle/Support/bin/texparser.py Latex.modified.tmbundle/Support/bin/texparser.py
--- Latex.tmbundle/Support/bin/texparser.py	2009-10-30 18:25:23.000000000 +0200
+++ Latex.modified.tmbundle/Support/bin/texparser.py	2009-10-30 18:26:29.000000000 +0200
@@ -122,6 +122,20 @@
         self.done = True
         print '</div>'

+class MetaPostParser(TexParser):
+    """Parse and format Error Messages from metapost"""
+    def __init__(self, btex, verbose):
+        super(MetaPostParser, self).__init__(btex,verbose)
+        self.patterns += [
+            (re.compile('^This is MetaPost'), self.info),
+            (re.compile('^! '), self.error),
+            (re.compile('^Transcript written'), self.finishRun)
+        ]
+
+    def finishRun(self,m,line):
+        self.done = True
+        print '</div>'
+
 class LaTexParser(TexParser):
     """Parse Output From Latex"""
     def __init__(self, input_stream, verbose, fileName):

The code above should be saved as Latex.tmbundle.diff file.

Patch details

Here are some details on the code, added by Latex.tmbundle.diff.

The diff file above customizes 3 files in Latex.tmbundle package: texparser.py, texMate.py, and texlib.js, located in Latex.tmbundle/Support/bin.

According to Latex.tmbundle coding style, the main functionality and dialog window modifications should be placed to texMate.py; MetaPost output messages parser should be added to texparser.py; and JavaScript function, wiring texMate.py functionality to dialog window button, should be added to texlib.js file.

Messages parser: texparser.py

The following code provides a very simple MetaPost error messages parser:

class MetaPostParser(TexParser):
    """Parse and format Error Messages from metapost"""
    def __init__(self, btex, verbose):
        super(MetaPostParser, self).__init__(btex,verbose)
        self.patterns += [
            (re.compile('^This is MetaPost'), self.info),
            (re.compile('^! '), self.error),
            (re.compile('^Transcript written'), self.finishRun)
        ]

    def finishRun(self,m,line):
        self.done = True
        print '</div>'

Functionality and template: texMate.py

A new function should be defined to determine target MetaPost .mp files (files) and run mpost command on them:

def run_metapost(mpostfile=None,texfile=None,verbose=False):
    """Determine targets and run the metapost command"""
    # find all the mp files.
    fatal,err,warn = 0,0,0
    mpfiles = []
    if texfile:
        basename = texfile[:texfile.rfind('.')]
    if mpostfile == None:
        mpfiles = [f[:f.rfind('.mp')] for f in os.listdir('.') if re.search('\.mp$',f) > 0]
    else:
        mpfiles = [mpostfile]
    for f in mpfiles:
        print '<h4>Processing: %s </h4>' % f
        runObj = Popen('mpost -interaction=nonstopmode -tex=latex '+shell_quote(f),
                       shell=True,stdout=PIPE,stdin=PIPE,stderr=STDOUT,close_fds=True)
        p = MetaPostParser(runObj.stdout,verbose)
        f,e,w = p.parseStream()
        fatal|=f
        err+=e
        warn+=w
        stat = runObj.wait()
    return stat,fatal,err,warn

The following piece of code provides additional command-line argument metapost:

    elif texCommand == 'metapost':
        texStatus, isFatal, numErrs, numWarns = run_metapost(texfile=fileName)

And finally, the typesetting dialog window template customization:

        print '<input type="button" value="Run MetaPost" onclick="runMetaPost(); return false" />'

JavaScript layer: texlib.js

Just add a function that is invoked when the “Run MetaPost” button is pressed:

function runMetaPost(){
    runCommand('metapost')
};

P.S.

WordPress sourcecode shortcodes are cool!

Today I think I shall be a performance expert.

• Funding Thinking Sphinx – Pat Allen is looking for sponsorship to spend a month working on the Thinking Sphinx plugin. That’s a good cause.
• Mu – Facebook Connect library written in JavaScript.
• Introducing Amazon RDS – The Amazon Relational Database Service – Essentially, canned MySQL servers in the Amazon cloud.
• nice_find – Find replacement for TextMate that uses grep or git_grep on your project.

waa… baru tau klo tema notepad bawaan mac os (textmate) yang keren2 ternyata bisa di convert ato diubah jadi tema-nya notepad++. meskipun versi terbaru dari notepad++ udah include banyak tema , tapi buat ni kan buat sesuatu yang beda gag papa kan..
kamu bisa pilih  tema textmate dari websitenya sendiri ato gugling bentar banyak banget. abiz itu donlod temanya trus  copy pake editor kesukaan kamu .
setelah itu buka website converter ini buat convert temanya . yah donlod deh tema yang udah jadi ,masukin ke folder themes di notepad++ kamu. terakhir buka notepad++ kamu klik setting > styler configuration >trus pilih tema yang udah di convert tadi.
selesai….
oiya donlod juga default fontnya textmate
monaco  disini 
inconsolata disini
dejavu san mono
Disini.
biar agak mirip tampilannya.
hhe…ribet banget yah mo nulis…
mpe disini dlu yaaa….

It looks like the Groovy and Grails bundles have moved to GitHub.  Here are the new instructions for installing the bundles.  First, you’ll need to install GitHub.  The easiest way is to use MacPorts:

sudo port selfupdate
sudo port install git-core

You can find other GitHub installation instructions at http://help.github.com/mac-git-installation/

Once you have GitHub installed, open Terminal and run these commands to install the TextMate bundles:

mkdir -p /Library/Application\ Support/TextMate/Bundles
cd /Library/Application\ Support/TextMate/Bundles/
git clone git://github.com/alkemist/groovy.tmbundle.git
git clone git://github.com/alkemist/Groovy-Grails.tmbundle.git

I hope this helps!

I just had to convert about 10 html pages to markdown to update an old site to use a django admin. I probably should have just done it by hand, but I don’t have any Vyvance around so fuck that. So I wrote this command for TextMate to switch out the basic stuff then I just had to glance over them and clean up anything that wouldn’t fit quickly into a regex.

#!/usr/bin/env python

import sys
import re

output = sys.stdin.read()

matches = [
	[r'</?strong>', '**'],
	[r'</?em>', '*'],
	[r'<h1>', '#'],
	[r'<h2>', '##'],
	[r'<h3>', '###'],
	[r'<h4>', '####'],
	[r'<h5>', '#####'],
	[r'<h6>', '######'],
	[r'</h\d>', '\n'],
	[r'</?p>', '\n'],
	[r'<br/?>', '  '],
	[r' {3,}', '  '],
	[r'<a\s+href="([^"]+)"\s*>([^<]+)</a>', '[\2](\1)'],
	[r'<li>', '- '],
	[r'</li>', ''],
	[r'\n{3}', '\n\n'],
]

for match in matches:
	output = re.sub(match[0], match[1], output)

print output

At the end of the day, you have to ship code. Or sleep.

• MySQL vs. PostgreSQL comparison – Reasonably fair, though it misses the fact that GUI tools for MySQL are generally better.
• Software patents should be abolished – Amen.
• script/nginx – Instructions for getting nginx + passenger running in your dev environment.
• RubyMine 2.0 Beta Overview – Some nice features coming in the next version of this IDE.
• Textmate Tip: Showing hidden files in the project viewer – Useful for editing .gitignore, among other things.
• Bumps – Project to extend Cucumber to work with Google Wave.

Запустив этот блог, первым желанием оказалось настроить возможность публикации сообщений с помощью Textmate.

1. Нижеперечисленные настройки подойдут для любого блога построенного на WordPress
2. С помощью Bundles > Blogging > Setup blogs
   необходимо настроить Textmate на работу с вашим блогом:

   			
   # List of Blogs
   #
   # Enter a blog name followed by the endpoint URL
   #
   # Blog Name      URL
     somename	     http://вашлогин.wordpress.com/xmlrpc.php
   			
   		

   Где somename – произвольное имя, которое будет использоваться для идентификации.
   Если блог размещен не на wordpress.com необходимо так же откорректировать и вторую часть url.
   Часть /xmlrpc.php не меняется.

3. Следующим шагом будет подготовка вашего сообщения. Для этого используем File > New From Template > Blogging.
   На выбор предлагается 4 варианта шаблонов: Markdown, Textile, HTML, Text.
   Я использую стандартный HTML, но ничто не мешает использовать другой.
4. Сгенерированный шаблон выглядит следующим образом:

   			
   Title: untitled
   
   Main entry text
   
   --------------------------------------------
   Main entry continued
   			
   		

   Title: untitled – это заголовочная часть вашего шаблона
   Main entry text – та часть сообщения, которая будет видна на главной странице
   Main entry continued – та часть сообщения, которая будет “под катом”

5. Поддерживаются следующие заголовки:
   • Blog: – имя вашего блога somename (п. 2) в конфигурационном файле
   • Title: – заголовок вашего сообщения в блоге
   • Category: – имеющиеся в блоге рубрики
   • Comments: – допускаются значения On или Off устанавливающие возможность добавления комментариев
   • Date: – если значение не задано, то сообщения публикуется сразу. Указывается в формате YYYY-MM-DD HH:MM:SS +/-0000
   • Slug: – задает ссылку на пост в блоге
   • Status: – известные мне статусы publish и draft
   • Keywords: – допускает перечисление ключевых слов через запятую. На мой взгляд в данной роли должен выступать заголовок Tags:, но он у меня почему-то не сработал

   Остальным заголовкам практического применения не нашел, так что если у кого-то есть по ним информация прошу поделиться.
   Все параметры кроме Title: являются необязательными.

6. Все! Ваше сообщение готово к публикации.
   Bundles > Blogging > Post to Blog
   При первой загрузке Textmate запросит имя пользователя и пароль. В дальнейшем пароль не запрашивается.
   Страница с просмотром опубликованного сообщения открывается автоматически.

Удачных публикаций и побольше читателей всем.

I love TextMate, working in it feels no natural. Although I have been an avid VI user, more and more nowadays I keep opening up TM. And it would be so nice if TM were available on Ubuntu.

And yeah trying to make gedit act like textmate sucks donkey b****

UPDATE: Ok so I tried netbeans and also ruby mine and I still think TextMate is the best.

I pulled the trigger and upgraded my main dev box to Snow Leopard. Took about 12 hours including some false starts, but all appears to be well.

• Growl 1.2b2 – With Snow Leopard compatibility for GrowlMail.
• Capistrano: Make sure there is something to deploy - Tip passed on by Matt Darby.
• openid_engine – Rails engine wrapper around the ruby-openid gem.
• A Lesson In Timing Attacks (or, Don’t use MessageDigest.isEquals) – Some background for folks who don’t understand the latest Rails security patch.
• Rails Magazine #4 – Free PDF now available.
• Make rvm and TextMate play nice – Patch from Peter Cooper.
• MailTags for Snow Leopard – Compatibility release, though major new features planned for some time this fall are still a mystery.
• prepend_engine_views – Code to add Rails engine views ahead of those in the app, from Eric Davis.
• Snow Leopard Ruby Development Environment Checklist / Gotchas – Notes from Ric Roberts.
• The Ultimate OS X Snow Leopard Stack For Rails Development – x86_64, MacPorts, Ruby 1.8/1.9, SQL Server, SQLite3, MySQL & More – Another install guide, this one MacPorts-centric.

I love WordPress’ sidebar widgets. I also despise coding them.

I love how they let me offload menial management tasks directly to clients, avoiding all the “Change this word to another word!” e-mails. But every time I code them, it seems to involve 15 minutes of Googling, copy-pasting from a previous widget, and looking at documentation.

So I created this TextMate “snippet” to make it easier:

class ${1:PREFIX_Name}_Widget extends WP_Widget {
	function $1_Widget() {
		\$widget_ops = array( 'classname' => '${2:CSS class name}', 'description' => '${3:Description}' );
		\$this->WP_Widget( '$2', '${4:Title}', \$widget_ops );
	}

	function widget( \$args, \$instance ) {
		extract( \$args, EXTR_SKIP );
		echo \$before_widget;
		echo \$before_title;
		echo '$4'; // Can set this with a widget option, or omit altogether
		echo \$after_title;

		//
		// Widget display logic goes here
		//

		echo \$after_widget;
	}

	function update( \$new_instance, \$old_instance ) {
		// update logic goes here
		\$updated_instance = \$new_instance;
		return \$updated_instance;
	}

	function form( \$instance ) {
		\$instance = wp_parse_args( (array) \$instance, array( ${5:array of option_name => value pairs} ) );

		// display field names here using:
		// \$this->get_field_id('option_name') - the CSS ID
		// \$this->get_field_name('option_name') - the HTML name
		// \$instance['option_name'] - the option value
	}
}

add_action( 'widgets_init', create_function( '', "register_widget('$1_Widget');" ) );

Just create a WordPress TextMate bundle, create a new snippet, paste in that code and give it a trigger like wpwidget. Then just type that trigger, press TAB, and you’ll be in the first field. Type, hit TAB to go to the next field. Places where you enter the same thing twice are handled—you only have to enter it once. There are some helpful comments that’ll guide you through the rest once you’ve filled out the basics. I find that with this snippet, I can code up a new widget in a couple of minutes, tops. This is definitely going to make it more likely for me to create a widget for a client instead of just cheating and editing their theme by hand myself.

These instructions are now outdated.  See http://charliesquires.wordpress.com/2009/10/02/installing-groovy-and-grails-bundles-in-textmate-updated/ for updated instructions. Thanks!

The Groovy website’s instructions for installing the TextMate bundle are very vague.  They point you to the bundle location and link you to the TextMate bundle instructions (which are useful, but long when all you want to know is how to install bundles).  Here’s all you need to do to install the Groovy and Grails bundles.

Open Terminal and run these commands:

mkdir -p /Library/Application\ Support/TextMate/Bundles
cd /Library/Application\ Support/TextMate/Bundles/
svn co http://svn.textmate.org/trunk/Bundles/Groovy.tmbundle
svn co http://svn.textmate.org/trunk/Bundles/Groovy%20Grails.tmbundle

How to configure in TextMate Bundle Editor:

Here the code:

#!/usr/bin/env ruby -w

TextMate.rescan_project