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
Hi,
Just to say there is a problem with the snippet "Insert Color..." Of Css,
when you have the 2 version of TextMate on you're mac TextMate 2 Call the
"Insert Color..." of TextMate 1 and so you loose the focus, but in the most
of case i'm unable to get the focus back and i will force to "Force Quit"
TextMate 2.
:)
Thanks.
PS : Can you give me a link to convert Tm1 Bundle to Tm2, because i can't
use "Google Closure Compiler" and it's borring to do with Tm1.
Reminder :
- File Browser, Random Expand => http://www.youtube.com/watch?v=X75SprY6nKchttp://www.youtube.com/watch?v=X75SprY6nKc
--
View this message in context: http://old.nabble.com/Insert-Color...-Problem-tp33076043p33076043.html
Sent from the textmate users mailing list archive at Nabble.com.
Hi,
Like many, I have been enjoying playing around with TM2, and have founds lots of things to like; for example, the use of .tm_properties files is great, as is the new file browser. I have, however, discovered a couple issues that prevent me from using TM2 for actual work, which in turn limits my ability to test it out seriously. One of these is probably a trivial issue and the others are minor and cosmetic, so this isn't really directed at Allan (who has more important things to do). However, I wonder whether others might be able to comment:
1) None of the bundle commands seem to work for me (e.g., TODO -> Show TODO List, Python -> Run Script, Mercurial -> Status, etc.) -- they all give the following error:
/Users/pschumm/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/escape.rb:23:in `e_url': private method `gsub' called for nil:NilClass (NoMethodError)
I am using a stock Lion setup (fully updated), with TM Version 2.0 (8971). I admit that I have not tried to look into this more carefully, in large part because I am completely unfamiliar with Ruby.
2) I can't seem to get the Wrap Column indicator line to show up, regardless of what I set Wrap Column to be; also, using the Wrap Column -> Other... menu item doesn't seem to work.
3) The font rendering seems a bit odd, or at least not like it is in TM 1.5, Terminal, etc. In particular, I typically use Monaco 9 pt. with antialiasing turned off. However, when I set TM2 this way, the letters are smaller than they are in an equivalent TM 1.5 or Terminal window and the interline spacing is much larger; in addition, the letters do not appear to be uniformly spaced. Can anyone comment on the possible reason(s) for these visual differences given the same font specification?
Any comments would be much appreciated.
Thanks,
-- Phil
