The more I use E the more I am liking it. I've researched for other editors with snippet support but things like jedit plugins come up. I tried it out but it just isn't the same, E has a bloat-free quality that is very alluring.
It has it's quirks though, mainly in the porting of Textmate bundles to Windows.
I wanted to be able to run makefiles and pipe the output through an error parser. There was already a command in there to do this so the process to run it would be:
- open the makefile
- make sure E knows it is a makefile
- press CTRL-R
This just gives the error 'target not found'.
Start editing the script in the bundle editor. The script appears to be a bash script so the learning curve is not too bad (e.g. no need to learn java).
Add 'pwd' to the script and it seems to be launching in C\Windows\System32 and there ain't no makefiles in there.
Add 'cd $TM_DIRECTORY' to the script to get it to cd to the directory where the makefile is and WAYHAY it runs and errors from the c compiler are listed in the results window. Click on and error and we are there at the source file/line.
This is how it should be.
I can believe that OSX is intelligent enough to not launch anything in the OSX equivalent of \Windows\System32.
And this will now work for ANY makefile, no dicking about creating new build configurations for each one, thank you Eclipse.
Peter's Moblog
Well, you're right: most problems with E come from porting the bundles from TextMate. Example: the Grails bundle has commands that seem to call some TextMate UI elements, which of course are not there with E. So that fails miserably and, opposing the way you could edit and fix the script above, here there's no workaround I can think of. Anyway, until I switch to the Mac and use the native Textmate (which means: as long as I have to stay on Windows), E seems a good compromise. Thanks!