A few issues in the syntax highlighting done by Perl's bundle.
The first one I think it's typically hard to get right: here-docs are
not recognised. This not only means that they are not colourised as
strings, but that their content can fool the rest of the highlighting,
for instance if there's an unbalanced quote. (Sometimes a fake comment
can help there though.)
POD sections are not recognised either, so not only they are not
coloured but Perl keywords are highlighted in regular English (for, if,
while, ...).
On the other side, hash elements are no correctly highlighted. In
$foo{bar} = "baz";
the red for variables goes beyond the "{" and stops at the "r":
$foo{bar
If "bar" is quoted the highlighting is correct though, curlies in black
and the string in green.
In the broken example I'd expect the curlies in black, and the key in
green because it's autoquoted by Perl. Green to the left of =>s would
be good as well, as words there are also autoquoted. Both conventions
for autoquoted stuff are followed by CPerl and the Perl mode for Vim.
q(), qq(), and their variants are not highlighted as strings either.
-- fxn
I just purchased TextMate and found some apparent bugs editing Perl and
Python. Which is the right address to report them?
-- fxn
PS: I would have liked new releases could have a new trial period. I
bought a license without being able to compare the current version with
the initial one.
>I just purchased TextMate and found some apparent bugs editing Perl and
>Python. Which is the right address to report them?
The language bundles are currently maintained by volunteer work. I
contributed the Perl bundle and according to
<http://wiki.macromates.com/textmate/show/Bundles102>, a bunch of
people contributed different Python bundles. Probably the best place
for bundle bug reports is this mailing list, with a subject like Perl
Bugs or something else clever to divert people who don't care.
What are the Perl bugs? They might be due either to my bundle or
underlying problems with TM.
- Eric
--
Eric Hsu, Assistant Professor of Mathematics
San Francisco State University
erichsu(a)math.sfsu.edu
http://math.sfsu.edu/hsu
Hi,
I would like to highlight the syntax as shown in the attached picture.
However, this matches the wrong brackets. Anyone any idea how I could go
about to better highlight this?
I guess it boils down to a not powerful enough syntax highlighting scheme
though :(. The thing I want to do is something like:
- match commands (begin with '\' followed by a word
- this can be followed by [\w+]
- and this can be followed by {.*}
And what I would like to do is apply the global patterns to the '.*'
mentioned above, and if nothing global matches, then apply a color.
Jeroen.
PS. I seem to remember something about using groups to define different
colors in a pattern, but I forgot how that works. Can anyone tell me how
that works and/or add that to the wiki ? :)
brilliant!
> Added history for find and replace strings. Currently it doesn't store
> options in the history (like regular expression or case sensitive)
That helps a lot... Can we save certain ones (esp grep searches) and
give them a name somehow (someday!)?
On reading the change notes in b10 I discovered the context menus for
selected text -- never used them previously but I love them.
Amazing progress as usual. Thanks Allan.
p.
sorry, I'm not quite sure I understand, are you saying that it does
work for you, or it doesn't? I've installed all the latest updates now,
but there is no change, it still doesn't launch, just appears in the
dock briefly for a split second and then vanishes again. I don't get a
crash message either.
I'm running 10.3.6 on a G4 dual 1.4Ghz.
weird.
Chris
Begin forwarded message:
> idem for me (Mac OS 10.3.6, last security updates done)
