howdy,
i just stumbled upon TextMate while looking for a native development
text editor and am _very_ impressed with it's featureset and believe i
will be purchasing soon.
i am wondering, however, if there is anyone out there who has
developed (or _loves_ to develop ;)) a syntax highlighting plist /
bundle for the Velocity Template Language
(http://jakarta.apache.org/velocity/vtl-reference-guide.html)? i am
terrible with regular expressions unfortunately, so i'm not having
much luck with it. it's basically a dynamic language like php or asp
and is mainly used in web (html type) files which can include css,
javascript, xml / xsl etc.... the best / closest type i've found to
work is the ASP style. it's _very_ close but would like to have
certain things highlighted differently and it's missing (obviously
since it's a different language) a bunch of declarations. i am
desperate for this type of highlighting.
if anyone is interested in helping me out, i could send an example
file that includes javascript, xml / xsl, css and Velocity markup. any
takers??
thanx in advance, jamal
Hi,
I'm attaching the compile script I use, or actually combination of scripts.
The compile script expects to get nothing as input and discards its output,
and the 'save active file before running command' thing should be on. The
command that runs it is:
compile-tm "$TM_FILEPATH" >/dev/null 2>&1 &
Two points:
- This reports on how things went via Growl---and it doesn't check if you
have it installed---so if you don't use it, you might want to go into the
'compile-report' script and change the Growl stuff to something else, like
maybe an AppleScript dialog box. (Just redirecting the output of the script
to a tooltip won't work without serious additional fiddling.)
- This tries to preview using TeXniscope.
The typeset script works analogously. I'm also attaching a script that goes
to the next TeX error by looking at the output file and piloting TM via
AppleScript (which is a bit slow and causes the 'go to line' dialog box to
appear briefly), and one that compiles the current selected text (but
requires the whole document as input).
Hope some of this might be of some use... It's not particularly earth-
shattering, but works OK for me.
On Dec 30, 2004, at 6:14 AM, Ivar Ã…sell wrote:
>
> From: Ivar Ã…sell <ivar(a)enskede.net>
> Date: 2004/12/30 Thu AM 05:14:54 CST
> To: TM Users <textmate(a)lists.macromates.com>
> Subject: [TxMt] Help with LaTeX-build command
>
> Hi!
>
> I would like to be able to do this in TM
>
> 1. select a .tex-file
> 2. run a macro that
> 2.1 selects all text
> 2.2 runs that text through a "tex-compiler" wich listens to stdin
> 2.3 pipe the results from the "tex-compiler" to the preview-app (can
> this too listen to stdin?) which show me a nice pdf
>
> And if I like the results I can save the .tex-file otherwise not.
> The main point here is that I which to see the pdf without having to
> save my .tex-file.
>
> Would someone help me with this?
> I have an idea on how this is supposed to be done...
>
> 1. record a macro (alt-cmd-m)
> 2. select all text (cmd-a)
> 3. filter through command (shift-alt-r)
> 3.1 input: selection
> 3.2 output: ? discard?
> 3.3 command: ??? something like "<build pdf> | open -a
> /Applications/Preview.app"
>
> I just read that "open" cannot read from stdin so I guess it has to be
> some other way around.
> Please, I'm really lousy at this stuff.
> Help would be much appreciated!
>
> Kindest Regards
> Ivar
>
> ______________________________________________________________________
> For new threads USE THIS: textmate(a)lists.macromates.com
> (threading gets destroyed and the universe will collapse if you don't)
> http://lists.macromates.com/mailman/listinfo/textmate
>
Hi!
I would like to be able to do this in TM
1. select a .tex-file
2. run a macro that
2.1 selects all text
2.2 runs that text through a "tex-compiler" wich listens to stdin
2.3 pipe the results from the "tex-compiler" to the preview-app (can
this too listen to stdin?) which show me a nice pdf
And if I like the results I can save the .tex-file otherwise not.
The main point here is that I which to see the pdf without having to
save my .tex-file.
Would someone help me with this?
I have an idea on how this is supposed to be done...
1. record a macro (alt-cmd-m)
2. select all text (cmd-a)
3. filter through command (shift-alt-r)
3.1 input: selection
3.2 output: ? discard?
3.3 command: ??? something like "<build pdf> | open -a
/Applications/Preview.app"
I just read that "open" cannot read from stdin so I guess it has to be
some other way around.
Please, I'm really lousy at this stuff.
Help would be much appreciated!
Kindest Regards
Ivar
Hi,
have you considered installing a web-based bug-tracking system
(bugzilla/RT/gnats/???) so users can submit bug reports and requests
for enhancements? It is much easier to track changes this way.
David
On Dec 30, 2004, at 0:25, Lars Pind wrote:
> [ default file/folder patterns ] So other people experiencing this
> problem, that's something to look for.
>
> Question for Allan: Is this on purpose?
The file/folder patterns are pretty much the result of evolution :)
I'm aware of the caveat about the preferences not reflecting existing
folder references. Interestingly I actually added this text to the
preferences pane yesterday -- but ideally it should affect non-changed
folder-reference patterns.
> It seems very confusing that there's a preferences pane setting that
> doesn't have any effect.
They are defaults (as implied by the label), i.e. used when creating
new folder references. But your critique is fair.
I'd like to be able to set my "indentation level" to 4 and leave the
tab stops at 8. That is, if I hit my tab key the cursor should move as
if my tabs stops are set at 4 (any any spaces required should be
added). If there are any actual tab characters in the file, the file
should display as if I had selected 8 as my tab size. (Basically this
is because I edit files that other people have edited using emacs which
"intelligently" uses tabs where it can to fill in sequences of 8
spaces.)
I was playing with the notion of expanding all the tabs to spaces so
that it will display properly even if I have my tab size set to 4, but
I'm afraid this will cause lots of extraneous differences when I check
in my changes to CVS.
Another item is that when I'm working in Tcl I want my indentation
level to be 4 characters. When working in PL/SQL I want it at 8.
(Probably in C or C++ I'd want 2 or 3.)
Allan,
It would be nice if the contextual menu for folders had an option
"Expand All" or some such that would expand all sub folders of the
currently selected folder.
Thanks.
Some features of the "bbedit" command line tool are discussed in this
review of BBEdit 8.0:
http://www.macdevcenter.com/pub/a/mac/2004/12/21/bbedit.html?CMP=ILC-
macrss&ATT=BBEdit+8.0++A+Developers+Viewpoint
For my taste, the notable bits are:
(1) The '--clean' option for suppressing the 'Do you want to save
changes?' dialog.
(2) The tool is installed from a button in the preferences.
Just some food for thought/discussion for the eventual TextMate
command-line tool.
Chris
> An Even Cooler Command Line
> I do quite a bit of work from the Terminal (well, iTerm, really)
> command line, and the new BBEdit Unix tool is useful in all the ways I
> wish the previous versions were. Before, I had to give BBEdit the -c
> switch to create a new document. Now, it figures that out on it's own.
> If I have the preferences set to open new documents in the front
> window, when the BBEdit tool opens multiple documents, they open in
> the same window.
>
> The latest update makes it even better. I can now pipe output from a
> command line process into BBEdit without creating an unsaved document.
> That way, I don't have to go through the annoying "Do you want to save
> changes" dialog. Once I've seen it and want to get rid of it, I just
> close the document.
>
> % netstat -rn | bbedit --clean
>
> I wish I had this feature for the "Unix Script Output" window I get
> when I choose "Run" from the "#!" menu (which I've set to
> Shift-Apple-R with the "Set Menu Keys..." item from the BBEdit menu.
>
> It gets even better, though. If I want to look at piped output, I want
> to read it from the top. Previously, BBEdit placed the curser at the
> end of the output, but I can now start off at the top of the output.
> % netstat -rn | bbedit --clean -view-top
>
> To get this updated version of the command line tool, you have to go
> to the Preferences. In the Tools pane, click on the button that says
> "Install Command Line Tools," which installs the latest versions of
> BBEdit and bbdiff.
>
>
>
With the holidays fast approaching and people drifting away from their
desks to do far more entertaining things than write code all day, I
though this was an appropriate time to:
a) wish everyone a very happy Christmas time, if they celebrate the
festival or not ;)
b) offer my thanks again to Allan for providing us with such a great
product. I spend all day, every day working with TextMate and it's the
first time I've actually felt 'at home' coding on the Mac since
switching last January.
That's all really :)
drew.
I'd like to make a bundle with PL/SQL syntax (didn't look like anyone
did that yet), but I don't see how to specify pairs of folding markers.
Here's an example of what's wrong:
PropertyList-Old.plist has these lines:
foldingStartMarker = "(\\{|\\()";
foldingStopMarker = "(\\}|\\))";
But what causes folds on bad blocks like this:
{ # curly brace
) # parenthesis
I'd like to do blocks like these:
IS -> END;
IF -> END IF;
( -> )
etc.
Possible? I see "pairs" of other things are being handled
(e.g.highlightPairs), perhaps we could do this too!
prl
