FWIW, one workaround is using TextMate::Process.run, which is quite well documented in the source (Support/lib/tm/process.rb) and is a lot more flexible than Executor. That said, I've thought about making Executor more flexible myself but haven't written any code to that effect yet.
The primary benefit of (unconditionally) parsing hashbang lines I can see is that it provides a way to specify file-specific options to the interpreter, a topic that came up w.r.t. C programs on IRC. Interpreter versions come to mind as well. Which other use cases am I overlooking here? Cheers, Martin On Mon, Feb 16, 2009 at 13:14, Matt Foster <[email protected]> wrote: > I'm playing with TextMate::Executor.run, trying to use it to write a > command to filter perl scripts through perlcritic. > > I've got the obvious: > TextMate::Executor.run(ENV["TM_PERLCRITIC"] || "perlcritic", > "--stern", ENV["TM_FILEPATH"]) > > But Executor sees the hashbang line in my script, and uses that instead. > > Is it possible to disable this selectively? or is there another workaround? > > Thanks in advance. > > Matt > > -- > Matt Foster | http://hackerific.net > _______________________________________________ > textmate-dev mailing list > [email protected] > http://lists.macromates.com/listinfo/textmate-dev > -- "when you don't create things, you become defined by your tastes rather than ability. your tastes only narrow & exclude people. so create." — _why _______________________________________________ textmate-dev mailing list [email protected] http://lists.macromates.com/listinfo/textmate-dev
