I just joined this list and seem to be having trouble posting, but
I'll give it another try.
I was wondering what the prevailing wisdom is regarding pattern naming
conventions for assembly languages. I'm working on a bundle for an
obscure chip (the long-discontinued Motorola DSP96002 which we still
use in a variety instruments on account of it being one of the few
DSPs which supports extended precision floats). So far, I've got
patterns like "assembly.opcode", "assembly.directive", and
"assembly.directive.macro", but I'm not sure this is the way to go.
Should these all be under "keyword", for example?
-Ted
Hi,
I can remeber that with the new OS X Leopard a new version of TM was
planned. Is that still in development and is there a date when it will
be released?
Thanks
Christian
Having problems with code-completion in Objective-C.
Basically, whenever I hit alt-escape for triggering a completion I get this:
sh: : command not found
/tmp/temp_textmate.I8XxsT:164:in /bin/bash: -c: line 0: unexpected EOF
while looking for matching `''
/bin/bash: -c: line 2: syntax error: unexpected end of fileshow_dialog'
from /tmp/temp_textmate.I8XxsT:118:in /bin/bash: -c: line 0:
unexpected EOF while looking for matching `''
/bin/bash: -c: line 2: syntax error: unexpected end of fileprint'
from /tmp/temp_textmate.I8XxsT:488
I am not sure, but I feel like I have seen errors like these pop up in
other bundles as well.
Any clues?
Thank you.
Howdy,
I was wondering if anybody else was having issues with they keyboard
shortcut for going to/from the main window to/from the project drawer?
Whenever I hit Ctrl+Tab together, it spits out a cryptic tmp file
message, like:
/tmp/temp_textmate.T5GF9m:4:in
Any ideas? I recall it worked at one point.
Cheers,
Matt
Has anyone done any work to update the objective C bundle to work for
iphone software development, namely the correct syntax highlighting of
NS* and UI* classes the SDK has introduced or looking up in the
documentation?
Thanks,
Dave.
I am new to this list and apologize if this topic has already been
covered.
I am trying to design a bundle for an obscure DSP assembly language,
and I have reached the point where I have got this sprawling regular
expression that can identify every instruction recognized by the
processor. It actually works quite well, and it's wonderful to see
the syntax coloring kick in.
So my question is about how best to identify assembly language
components in terms of themes. Are there any precedents in this
regard? For the time being, I am using two main categories:
assembly.opcode
assembly.directive
I have also broken these down into the likes of
assembly.directive.macro and assembly.opcode.modifier. The latter may
be a peculiarity of the language I am using, which has constructs like
this:
tst d0
add d1,d2 ifeq
This tells the processor to add data register d1 to d2, but only if
the value of d0 tested zero. The "ifeq", then, is what I am referring
to as an opcode modifier, for want of a better term.
Anyway, I'm not sure if I am going about this right, or if it all
needs to go under keyword or something. Any suggestions?
-Ted
Hi everyone,
I've recently started coding in Objective-C and noticed that none of
the comments in my ".m" source files are syntax colored. CNTL-SHIFT-P
shows the comments' scope as:
source.objc
meta.implementation.objc
meta.scope.implementation.objc
Essentially, the same scope as the rest of the code. For comments, I
would have expected to also see something like:
comment-line-double-slash.objc
And also:
comment-block.objc
Any ideas how I can remedy this? BTW, I'm using TextMate v1.5.7
(build 1455). Have I somehow unwittingly screwed up my Objective-C TM
bundle?
Thanks,
--Cliff
