It would be nice if I could specify a per-file-type command. The same key stroke would run different commands for different file types. For example, I'd like to run "rake" for Ruby files, "ant" for Java, etc.
Actually, I'd like TextMate to read my mind and figure out if I use make or Ant for a particular project. Hmm...that gives me an idea for a script: start at the current directory, looking for a makefile, Rakefile, or Ant build.xml file. If none is found, look in the parent directory. Lather. Rinse. Repeat. Execute whichever comes first. I already have a script that looks for makefiles this way; it shouldn't be too difficult to modify to look for the three kinds of files.
Here's a really wacky feature request: a way to specify an argument to the command each time I run it. When I'm developing, sometimes I want to run "make" then "make set-up-test-data" then "make test", or do things in a different order.
Thanks for listening.
Jim
On 19. Oct 2004, at 13:02, Jim Menard wrote:
It would be nice if I could specify a per-file-type command. The same key stroke would run different commands for different file types. For example, I'd like to run "rake" for Ruby files, "ant" for Java, etc.
As of such, you can check the extension in your command by looking at $TM_FILEPATH
Here's a really wacky feature request: a way to specify an argument to the command each time I run it. When I'm developing, sometimes I want to run "make" then "make set-up-test-data" then "make test", or do things in a different order.
I think this will be possible when I introduce project-specific shell variables, as requested by Ivan (IIRC).
Kind regards Allan