I am a beginner with textmate, and I wondered where I could
get soem kind of tutorial for it. Not for the basic editing
fuvnctions, but for customization, what textlate can do apart
editing, etc.
I tried the wiki, but I'm much more at ease with a document I can
print and read. Is tehre something like that ?
--
Erwan David
For those who got r540 and is on a Panther system, here's a direct
link to the previous build:
http://macromates.com/textmate/build/TextMate_r528.tbz
I do plan to continue with Panther support, but with the current
developer tools, it seems to be Panther or i386, but not both, if I
want to use libcurl -- it may take a day or so before this is sorted
out. Meanwhile the auto-update won't let Panther systems update to r540.
When I hit enter on <div>|</div>, I get this:
<div>
[tab]|
</div>
which is great, I can immediately begin typing and nesting and so on.
I'd like this behaviour also for the p tag for instance, and all the
other block tags. Also for all xml tags that aren't ended with a /
(that is, not for <tag/>, but for <tag></tag>).
Andreas
I added the following to my javascript bundle, over the normal
function detection code (but that wouldn't make any difference, right?)
{ name = "meta.function.js";
match = "^\\s*([a-zA-Z_]\\w*):\\s*(function)\\s*\\(([^)]
*)\\)";
captures =
{ 1 = { name = "entity.name.function.js"; };
2 = { name = "storage.type.function.js"; };
3 = { name = "variable.parameter.function.js"; };
};
},
{ name = "meta.function.js";
match = "^\\s*(var\\b)?\\s*this\\.([a-zA-Z_]\\w*)\\s*=\
\s*(function)\\s*\\(([^)]*)\\)";
captures =
{ 1 = { name = "storage.type.js"; };
2 = { name = "entity.name.function.js"; };
3 = { name = "storage.type.function.js"; };
4 = { name = "variable.parameter.function.js"; };
};
},
the first should match functions like
functionName: function(arguments) { ... }
and the second
(var) this.functionName = function(arguments) { ... }
with the first var being optional.
Is it correct? It seems to work but I don't dare trust my RegExp
skills ;)
Any other comments?
Andreas
Hi,
I don't suppose it would be a quick fix to make the 'go to symbol'
dialog behave in the same way as the 'go to file' dialog? Or even
just make the list of symbols sortable?
Regards,
Graeme
--
Mail: mathie(a)woss.name | Web: http://woss.name/
AIM: Math1e | PGP: 1024D/D72F2737
I tried to contact 'Wes' about the Lua bundle mentioned on the Wiki
bundle page, but never got a response, and decided to just write my own.
I think the syntax highlighting is correct - it includes appropriate
highlighting for all the keywords as well as all the built-in library
functions.
In addition to some convenient Snippets for code forms that I
personally write frequently, I've added 'cheat sheet' Snippets for
all the global built-in functions and the table, string, and
coroutine libraries. These tab trigger Snippets fill out the argument
list with descriptive names, including which parameter(s) are
optional. When parameters are optional, I included the preceding
comma in the placeholder, so that tabbing through the function and
pressing delete will remove any undesirable optional parameters.
(I got tired of entering all the Snippets, and have not yet added
Snippets for the math, os, or io libraries.)
You can download my bundle from http://phrogz.net/tmp/
Lua.tmbundle.tar.gz
(Is anyone else using programming Lua on MacOS X? :)
Hi all,
I just managed to crash TM. Do you want me to put the crash log
somewhere? It seems a bit big to post here I certainly will if you
would like me to.
-Eric
Hi everybody,
It took me a little while to come up with this, what with finding the
correct command and environment variable etc., so I figured that I
might as well share it here. When you compile something with TeX or
LaTeX in Terminal.app instead of say TeXShop or our favourite editor
and an error message like this pops up
-----------
! Missing $ inserted.
<inserted text>
$
l.7
?
----------
you can enter 'e' to edit that file and correct the error. The
problem on a vanilla TeX installation is that the vi editor is used
for this. To use TextMate instead you can put this command in
your .tcshrc
setenv TEXEDIT "mate -w -l %d %s"
and on entering 'e' TextMate will be launched and the caret will be
placed on the line where the error occured. For the bash shell the
above command would be
export TEXEDIT="mate -w -l %d %s"
I hope you'll find this useful, I certainly do :-)
Bye, Thomas
