In TM2 when I open a new window and then open the file browser for that
window, the file browser shows my home directory at the top and then
proceeds to churn away (I guess it is indexing the folders?) and it expands
each and every folder recursively which takes a long time. While this is
happening TM is not usable as I get the spinning wheel. Plus when it has
finished all of the folders are expanded which makes it quite difficult to
browse files without manually collapsing each folder.
I'm first time on TM mailing lists, so don't kick me hard.
I'm wondering if it is possible to add hotkey to switch between File Browser and File View Window?
Also would be cool to be able to open file with a hotkey from File Browser.
Maybe this is odd, bud I didn't find it in archive.
Thanks!
One thing I am missing in TM2 is "Save files when focus is lost".
I'm finding it very difficult to teach myself to edit > save > test in
browser....
Am I missing where that can be set?
If it's not a current feature then I'll toss it on the request pile.
Thanks,
J-
Since C grammar is intended to be the base for other grammars such as C++ or Obj-C it uses `include = '$base'` instead of `include = '$self'` for all recursive sub-block parsing to point back to original grammar (if possible). This works perfectly well for standalone C or C++ file, however when trying to embed C source into other language we get a problem, i.e. for Ruby grammar:
# trying to embed something into Ruby
variable = <<-C
/* we are parsed by C grammar here */
enum {
/* ooops this comment isn't parsed anymore by C grammar but Ruby again! */
}
C
Problem is on '{' which starts new C block, that does `include = '$base'`. Unfortunately $base is Ruby here not C. Same if we change C into CPP in the example above, $base is still Ruby.
I can see two solutions here:
(1) caller should be able to block/change $base i.e. using some new keyword:
{ safeInclude = 'source.c'; }
or
{ base = 'source.c'; include = 'source.c'; }
(2) callee should be able to specify language grammars that are allowed to be base for it.
Or maybe there's already some undocumented solution?
Cheers,
--
Adam Strzelecki
Hello,
I am trying to create a bundle where in the particular language after a function definition you would call that function with:
[code....]
function my_function_name
.
.
code
.
.
end function
...more code...
call my_function_name
[/code....]
Now for the question to the TxMt gurus:
How would I make it so the "my_function_name" has a different color after the "call" keyword ?
I have already made the "call" to be a reserved keyword colored blue but if would be nice to have the "my_function_name" function colored red or some other catchy color after the word "call"
Is that possible and what would be the syntax for the bundle?
Thanks in advance.
John
> I should have mentioned that if I turn soft-wrap on, then the right margin indicator becomes visible; it's only when soft-wrap is off that it's invisible. Unfortunately, that's exactly when you need it.
I have the exact same issue and it seems small but it's pretty much the only thing stopping me from using TM2 full time. Any clues how to turn this on or when it might be implemented/fixed?
Hi all,
Just downloaded and started using TM2, and I've found an issue when opening a new tab.
When hitting Option + Command + N, a new tab is opened, but also all of the folders in the file view on the left become expanded. After this TM2 becomes unresponsive and I have to force close it.
Has anybody else experienced this issue?
I'm running TM2 v2.0 (8956) on a MacBook Air with Lion 10.7.2.
Cheers,
Gaz.
First time posting to the list - please be gentle....
So, I open a folder into Textmate2 (8971) and set View...Soft Wrap to off
(unchecked).
Do some work...open another file...go back to the original file, Soft Wrap
is now checked without me doing anything to turn it on.
Am I missing something? Is this a case where I need a .tm_properties file
in the folder I'm working in?
(Otherwise I'm really liking how TM2 is working so far)
J-
Hi,
since the first "official" Alpha version, TM2 allows themes to resize text in certain scopes (headers, etc.). The markdown bundle does this, for example. Is it possible to completely disable this feature, as I generally don't find it very pretty (which seems like a tuning issue) and it does have some weird issues with code blocks (erratic resizing of single lines)? I couldn't find it in any of the tm_properties guides.
Best regards,
Florian
