The behavior of the files list changed in TextMate 2. In TextMate 1, it included the current file, but in TextMate 2, the current file is not in the list.
I know that sounds like not a big deal, but it can be a problem with large projects containing many files. On several occasions I have opened the files list, typed a few characters, and spent the next two minutes freaked out and confused because the document I know exists is "missing", only to realize it's right under my nose.
Any chance we could get the old behavior back? Thanks,
Trevor
For example, I would like to do this:
windowTitle = "$TM_DISPLAYNAME – ${TM_DIRECTORY/$TM_PROJECT_DIRECTORY//g}"
where the string in TM_PROJECT_DIRECTORY is being removed from the string in TM_DIRECTORY
Thanks!
Michael Johnston
lastobelus(a)mac.com
We've discovered (naturally in an unpleasant way)
that TM (1.5.10) will translate CR (0x0d) in a file to
LF (0x0a) on save - even when the Line Endings setting
"Use for existing files as well" is not checked.
This seems like a bug, as it seems the settings are to
leave existing files alone with respect to potential
line ending characters.
Is this a known issue?
Thanks much,
-eric
Hello folks.
After an extended break from Textmate I am very happy with the TM2
alpha and looking forward to getting to grips with this app again.
There was a thread in mid-December about themes where Arlo was looking
to turn of anti-aliasing. Did an answer ever come out? I'd like to
change the default Markdown presentation as I don't like different
fonts in my text files - I've searched but can't find a description of
what can and can't be amended, or how.
Thanks!
Nigel
I've the same problem. I can confirm that folders expand when opening a new
tab under certain (unknown) circumstances.
I think that the folders expansion is what makes Textmate2 not responding.
It takes some minutes to return responsive, it depends on how many folder
levels has to expand.
Being not able to find a way to collapse all the folders back with a single
command, I'm using another way to create files.
Due the fact that neither Finder allows you to create new files, I select
the folder in the TM2 project drawer and open a new terminal from TM2 using
the shift+Ctrl+O shurtcut and operate from there (also because is easier to
add them to git then).
Of all the TM2 bugs this is absolutely the most annoying and work breaking.
--
View this message in context: http://old.nabble.com/TextMate-2-freezing-when-creating-a-new-tab-in-a-larg…
Sent from the textmate users mailing list archive at Nabble.com.
Textmate's Ruby grammar appears to get confused by the
foo = {
"bar" => 42
}
but adding a comment after the closing brace throws things off:
foo = {
"bar" => 42
} # comment breaks indentation
I tend to use "Indent Line" (⌥⌘[) quite a bit, and this behaviour makes it pretty hard to easily re-indent nested data structures, e.g.
data = {
"jim" => {
"name" => "James Jameson"
},
"bob" => {
"name" => "Robert Robertson"
},
"billy" => {
"name" => "William Williams"
}
}
The problem seems to be limited to Ruby mode; other language grammars (e.g. Java, Javascript) seem to be unaffacted.
Am I the only one experiencing this? Any bright ideas?
--
cheers,
Mike Williams
Happy New Year everyone-
I know "scope" probably isn't the right word here, but this is what
I'm struggling with:
I work with a fellow who uses TextWrangler, and for a bunch of legacy
reasons, has language files (Forth) that have no extension to indicate
their contents. I'd love to be able to open these and have them
automatically be parsed as Forth source. This is an obvious solution
for a folder:
[ "cocoa/*" ]
fileType = "source.forth"
But some folders also have other file types in them with extensions:
.txt, .prf ,etc.
So it'd be great to say something like this:
[ "cocoa/*" ]
fileType = "source.forth"
["cocoa/*.{txt, prf}"]
fileType = "text.plain"
and have any text or preferences file be treated as text, and anything
else be considered a Forth source file.
Is this the way that TM2 works? Or are all specifications assumed to
be mutually exclusive?
(And if they are expected to be mutually exclusive, how are glob
conflicts handled?)
Thanks! Charles
Hi,
I'm working in a large project (3000+ files and directories) and can consistently cause TM2 to hang up under the following circumstances:
* In the project file browser, expand a large number of directories, or a very deep directory tree (not sure exactly which, but appears to be related to the number of directories expanded)
* Create a new file in a tab using Opt-Cmd-N
* TM2 freezes.
I've noticed the following symptoms (in addition to the freezing):
* The cursor is not the regular text insertion cursor but is a crosshair.
* The scroll bar in the file drawer appears to periodically jump around
* Spinning beach ball comes and goes
I'm not sure if waiting it out would work, I've waited for a few minutes before force-quitting.
The freezing, etc., doesn't occur if all the top level directories are collapsed. I can create a new document with no trouble.
This is the kind of thing I'm looking at in my project drawer when the freezing happens: http://cl.ly/382p0Z124239253E1M3o. (You can see in that picture that pretty much every directory in the tree is expanded. I think this may have happened the first time I encountered the bug, as I certainly didn't expand all those manually.)
Hopefully that will help you reproduce the bug. Has anyone else experienced this?
Adam