> From: Trevor Harmon <trevor(a)vocaro.com>
> Message-ID: <AA646749-1963-48F8-BA06-2DEEB46200DF(a)vocaro.com>
>
> I was thinking it might be cool if TextMate had visual tabs like
> OmniWeb or Shiira:
>
> http://www.mathgamehouse.com/images/phillryu/shiira2full.png
>
> But after testing the idea I've decided it just doesn't work with
> text. Web pages with graphics can be distinguished at thumbnail size,
> but source code files can't.
Reminds me of this:
http://basildoncoder.com/blog/2008/03/21/the-pg-wodehouse-method-of-refacto…
Be well,
Will :-}
Hello,
Maybe I'm just not understanding how it works, but while in an HTML document
I wanted to insert a DocType. I pulled up the Insert Bundle item window
(Ctrl-Cmd-T) and tried typing "doctype" to see if the shortcut came up, but
it did not. I just looked at the window again, and I see, right in the first
page of items "Insert DocType", but when I start typing "doctype" it goes
away, not matching what I'm typing. Am I missing something?
Thanks
John
In TextMate, buffer tabs are automatic: A new tab is always opened
whenever you click on a file in a project drawer. After a half hour of
navigating source code, I suddenly find dozens of tabs open at the top
of my editor window, but I can only see a few of them. This makes the
tabs feature basically unusable.
In contrast, web browser tabs operate quite differently. They're
manual instead of automatic: A new tab doesn't open unless you
explicitly open one. Until then, new data is displayed in the current
tab. TextMate's tab feature would be much more useful to me if it
worked this way --- the way web browsers do.
Does anyone prefer the current (automatic) behavior?
Trevor
So,
I've just installed the AS3 bundle from the repository in TextMate and
thought I'd share the steps I had to go through in order to make it
work, partially so I have a document explaining what I had to do (if I
need to do it again) and to help others who might be stuck.
Message for Simon Gregory: This was the bundle I downloaded from the
repository so it's possible that the svn version is b0rked... :(
I have an up to date version of TM on Leopard, and I used the "Get AS3
Bundle.sh" script that I downloaded a short while ago. Unfortunately
I couldn't find the site where it came from but it just appears to
grab the latest version from the repository by svn so it can't do that
much.
First, I got the wonderful error dialog:
> The “ActionScript 3” bundle located in ~/Library/Application Support/
> TextMate/Bundles could not be loaded and will be skipped. The
> contained info.plist appears to be corrupt or missing.
What's going on here? No idea. So I looked at the plist file in
question and found what looked like a half failed diff at the bottom:
<<<<<<< .mine
... some txt
=======
... other text
>>>>>>> .r10513
This is present in a bunch of files, I have so far found it in
build_with_fcsh.sh and asd.rb. Anywho, I took that out of the plist
file, probably breaking it slightly but at least TM now loads the AS3
bundle.
Next I created a new, blank AS3 project. Make a more or less empty
class and "Build with FCSH". Nothing, no output, no error, no
feedback, nothing. Build with MXMLC, a window pops up telling me
there's 0 errors and a successful build, but no .swf file was produced
in the deploy/ folder. Try the "Build (custom)" option, it tells me
the script is not executable. Joy. So I run the supplied compile.sh
script manually by opening the script and pressing Apple-R to run it.
TM alerts me that the script is not executable, so I make it so. OK,
so now it runs.
However, still nothing coming out of mxmlc, still 0 errors. What
happens when I run mxmlc on it's own? I get this wonderful error:
-bash: ./mxmlc: /bin/sh^M: bad interpreter: No such file or directory
Joy. That error is familiar, usually found when running a binary
built for a different architecture, but that wasn't the problem.
mxmlc turns out to be a shell script that runs slightly different
commands for windows and unix. Turns out that the default file
supplied by Adobe is also in DOS encoding (funny line endings). So,
open the file in vim and type:
# vim ./mxmlc
:set ff=unix
:wq
And the script now runs mxmlc properly. I also had to chmod a+x in
Flex/bin/* as well.
OK, so building in mxmlc now works but I know that it's slow and I'd
rather use fcsh to do my compiles. So I try building with fcsh and
get even less reponse, no progress bar, no iTerm window, nada. OK,
stay calm...
So I check the encoding of the fcsh script supplied by Flex, it too
was in DOS format so I converted it back to Unix. That script now
fires up the fcsh compiler so that part worked. Next, why was the
build command silently failing? Open up the Bundle Editor and edit
the "Build (fcsh)" command to show output as HTML. This revealed a
syntax error in the build_with_fcsh.sh script. Find the script, open
it in vim and I found the same sort of failed diffs as I found in the
plist file.
This time I just copied the r10513 file over the existing one:
# cd "/Users/gaby/Library/Application Support/TextMate/Bundles/
ActionScript 3.tmbundle/Support/bin/"
# cp build_with_fcsh.sh.r10513 build_with_fcsh.sh
Now the script works, fcsh works, mxmlc works and I have finally got
a .swf file being output into the deploy folder. Sorry for the length
of this rant but my hope is that if anybody else is fighting with AS3
under TextMate, hopefully this might shed some light on problems
they're having.
Gaby
--
Being drunk is feeling sophisticated without being able to say it.
http://www.playr.co.uk/
Hi,
yesterday I installed TM plus some bundles on my new Mac. Among others
I also installed the R bundles. These bundles have some Ruby functions
which insert something into the current doc. Fine. But there's a
"problem" with the Pristine's bundle folder permissions.
I get for instance that warning:
... warning: Insecure world writable dir “DIR” in PATH, mode 040777
This means that the bundle folder has also set the write access rights
to group and others. The way to fix this is to execute: chmod og-w
'DIR' .
My question is whether this is a general thing; and if yes, whether it
could be fixed in TM internally?
Cheers,
--Hans
Hi,
I have a problem. I took the finite example coming from progress.rb to
figure out how to cancel the block running inside of
TextMate.call_with_progress.
If I have a TM Ruby doc with the code and press apple+R the Cancel
button works. If I have the same code in a tmCommand the Cancel button
does not work, even if I store the code as Ruby file somewhere.
Is this something which should be fixed in the future?
Is this my fault? If yes, how is the correct syntax or workaround?
Thanks in advanced,
--Hans
I'm building up a grammar for the Confluence wiki markup, and I'm
having trouble with tags that take a list of parameters.
Tags look like this (all strings are examples only):
{noparams}
{oneparam:key=10}
{twoparams:keyOne=value|keyTwo=2%}
{threeparams:keyA=a value|keyB=another value|keyC=a third value}
So the tag name can stand alone, or if it is followed by ':', it takes
a '|'-delimited list of key=value pairs.
When I use the grammar fragment at the end of this message, noparams,
oneparam, and twoparams are highlighted as I expect. When there are
three or more parameters, the first and last parameters are
highlighted as I expect, but the middle ones are highlighted as plain
entity.confluence.
I'm sure this is a defect in my match= regular expression, but I'm not
seeing it. Could someone enlighten me, please?
— F
{ name = 'entity.confluence';
match = '(?x:
\{
([-[:alnum:]]+)
(:(\w+)=([^|}]+)
(
\|(\w+)=([^|}]+)
)*
)?
\}
)';
captures = {
1 = { name = 'keyword.confluence'; };
3 = { name = 'support.confluence'; };
4 = { name = 'string.confluence'; };
6 = { name = 'support.confluence'; };
7 = { name = 'string.confluence'; };
};
},
I added a bundle for JSFL (Flash JavaScript API) to the review section
of the repository a few weeks ago. Personally I only ever really use
jsfl to batch process images, swfs, video etc, once a month or so but
even with my limited use am sure the bundles solid enough.
If anyone has had chance to test it and has any suggestions please let
me know (and hopefully I can actually get a bundle out of review...).
Cheers,
Simon
Hi,
I'm just playing with Oniguruma's nested levels etc. In principal it
works brilliant, BUT it could happen that the regexp engine runs in an
eternal loop with no chance to cancel that loop.
Example:
<html lang="en">
<body>
<div>
<div id="2">
<p>blah</p>
</div>
</div>
</body>
</html>
regexp: (one line!)
(?-i)(?<element>\g<stag>\g<content>*\g<etag>){0}(?<stag><\g<name>
\s*[^>]*>){0}(?<name>[a-zA-Z_:]+){0}(?<content>[^<&]+(\g<element>|[^<&]
+)*){0}(?<etag></\k<name+1>>){0}\g<element>
Place the caret within the p tag and find previous match (SHIFT+APPLE
+G) and repeat it. Fine this works. The same also works for find next
match.
But the regexp CANNOT handle up to now tags like <img src="foo">.
So if you have e.g.:
<html lang="en">
<body>
<div>
<img src="foo">
<div id="2">
<p>blah</p>
</div>
</div>
</body>
</html>
[ATTENTION TextMate will freeze!!!!]
place the caret inside of the p tag and press three time SHIFT+APPLE+G
and TM freezes. You only can "force quit". Attached is a part of the
error report.
Of course, this is a problem of the regexp but if one wants to develop
such a regexp such errors could appear. The question now is how to
interrupt such an eternal regexp loop??
To be honest I have no idea but maybe one could listen to the keyboard
event (APPLE+.) inside of the regexp function.
Cheers,
--Hans
Error report:
223 __Z18view_find_previousPN4text4viewE + 1075 (in TextMate) [0x9c719]
223 __ZN9oniguruma4findEPtiiPKNS_6ptrn_tEii + 115 (in TextMate)
[0xf6639]
11 _onig_search + 414 (in TextMate) [0x161bba]
1 _onig_is_in_code_range + 67 (in TextMate) [0x15c2c1]
1 _utf16le_mbc_enc_len + 22 (in TextMate) [0x16361a]
1 _utf16le_mbc_enc_len + 11 (in TextMate) [0x16360f]
1 _onig_is_in_code_range + 29 (in TextMate) [0x15c29b]
1 _onig_is_in_code_range + 31 (in TextMate) [0x15c29d]
1 _onig_is_in_code_range + 88 (in TextMate) [0x15c2d6]
1 _onig_is_in_code_range + 11 (in TextMate) [0x15c289]
1 _onig_is_in_code_range + 4 (in TextMate) [0x15c282]
1 _mem_is_in_memp + 4 (in TextMate) [0x15c249]
1 _mem_is_in_memp + 5 (in TextMate) [0x15c24a]
1 _utf16le_mbc_to_code + 17 (in TextMate) [0x163651]
8 _match_at + 3858 (in TextMate) [0x15d291]
7 _match_at + 10242 (in TextMate) [0x15eb81]
7 _match_at + 8800 (in TextMate) [0x15e5df]
7 _match_at + 3848 (in TextMate) [0x15d287]
7 _match_at + 3814 (in TextMate) [0x15d265]
6 _match_at + 8811 (in TextMate) [0x15e5ea]
6 _match_at + 339 (in TextMate) [0x15c4d2]
6 _match_at + 3842 (in TextMate) [0x15d281]
6 _match_at + 10259 (in TextMate) [0x15eb92]
5 _match_at + 8784 (in TextMate) [0x15e5cf]
5 _match_at + 6579 (in TextMate) [0x15dd32]
4 _match_at + 2121 (in TextMate) [0x15cbc8]
4 _match_at + 3834 (in TextMate) [0x15d279]
4 _match_at + 10216 (in TextMate) [0x15eb67]
4 _match_at + 6626 (in TextMate) [0x15dd61]
4 _match_at + 3825 (in TextMate) [0x15d270]
4 _match_at + 6599 (in TextMate) [0x15dd46]
3 _match_at + 341 (in TextMate) [0x15c4d4]
3 _match_at + 8795 (in TextMate) [0x15e5da]
3 _match_at + 11214 (in TextMate) [0x15ef4d]
3 _match_at + 3387 (in TextMate) [0x15d0ba]
3 _match_at + 8790 (in TextMate) [0x15e5d5]
3 _match_at + 8806 (in TextMate) [0x15e5e5]
3 _match_at + 3434 (in TextMate) [0x15d0e9]
3 _match_at + 2195 (in TextMate) [0x15cc12]
3 _match_at + 6614 (in TextMate) [0x15dd55]
2 _match_at + 11317 (in TextMate) [0x15efb4]
2 _match_at + 3816 (in TextMate) [0x15d267]
2 _match_at + 6593 (in TextMate) [0x15dd40]
2 _match_at + 299 (in TextMate) [0x15c4aa]
2 _match_at + 6590 (in TextMate) [0x15dd3d]
2 _match_at + 2108 (in TextMate) [0x15cbbb]
2 _match_at + 1446 (in TextMate) [0x15c925]
2 _match_at + 10232 (in TextMate) [0x15eb77]
2 _match_at + 3811 (in TextMate) [0x15d262]
2 _match_at + 6616 (in TextMate) [0x15dd57]
2 _match_at + 2198 (in TextMate) [0x15cc15]
2 _match_at + 10238 (in TextMate) [0x15eb7d]
2 _match_at + 10227 (in TextMate) [0x15eb72]
2 _match_at + 8798 (in TextMate) [0x15e5dd]
2 _match_at + 10143 (in TextMate) [0x15eb1e]
2 _match_at + 2084 (in TextMate) [0x15cba3]
1 _match_at + 16465 (in TextMate) [0x1603d0]
1 _match_at + 3408 (in TextMate) [0x15d0cf]
1 _match_at + 11320 (in TextMate) [0x15efb7]
1 _match_at + 6548 (in TextMate) [0x15dd13]
1 _match_at + 2146 (in TextMate) [0x15cbe1]
Hello,
which switch do I have to turn on to get more verbose debugging output
from the latex bundle?
I'm using pdftex as the typesetting engine?
Thanks,
Jan
