22 Dec
2005
22 Dec
'05
12:02 p.m.
On 22/12/2005, at 12.35, Dave Baldwin wrote:
I have spend some time looking at the Run script and
the tmruby
file and basically understand what they are doing. I don't think
it is too hard to get the behaviour I want, and having a
TM_MAIN_RUBY or some such variable as you have for Latex looks like
the best way, particularly as this can be bound to a project.
Thanks for this tip.
I am pretty sure the tmruby command should be left untouched, and all
that is needed is a small command to do the following:
[[ ${TM_WARN_LEVEL:-0} > 0 ]] && w='-w' || w=''
cd `dirname "$TM_RUBY_MASTER"`
${TM_RUBY:-ruby} $w -- "$TM_BUNDLE_SUPPORT/tmruby.rb" `basename
"$TM_RUBY_MASTER"`
(not tested)
My main frustration is not being able to click through
on reported
errors. While I understand what the script is doing, I don't
understand why the error produces different results when run from
the terminal or within TextMate.
It produces different results due to the nice formatting applied..
that the result doesn't WORK then, is a bug in tmruby.
1. In 'top level' line in terminal just
includes the file name
while in the HTML it has the full path name in the url (and I can
click through here).
2. The lower level lines in terminal have the fully qualified path
name, but the HTML is relative to the top level file (and clicking
through just opens an empty window
Ok, so that's an error. I'll have a look.
Maybe the cause is the fork?
I don't know, but the fork very needed at this time at least. There
might be other ways to do it.
-- Sune.