I've seen some different behavior and I'm assuming the gutter has gotten some love lately.
Unfortunately I've just found a bug where the gutter will fill half the window, over the text, its non-fatal and only triggers on the HTML drawer being resized, so its probably pretty low priority, but its easily reproducible on my system.
It seems to me the text content must be longer than the page window, and it must be scrolled some.
Gist of the markdown used is here:
https://gist.github.com/anonymous/d1b02248ac263b868f15
An Image here:
http://i.imgur.com/YnLrVBq.png
And here's a video of the bug:
http://screencast.com/t/ib7nlyVh
Im using Command + Option + Control + P to show and Command + Option + Control + H to hide the drawer.
If the app looses focus, the bug fixes itself when it gains it back.
Thanks guys. Keep up the good work!
--
Graham P Heath
I started trying out the new gutter mark functionality. I noticed when I
add a gutter mark with a value with a single line, the popover looks
kind of odd. It looks like a graphical bug [1]
[1] https://drive.google.com/file/d/0B7UtafxGD9vELTRJbkNJVm9md0k/view
--
/Jacob Carlborg
I have also had problems with Yosemite and Latex. Besides frequent crashes upon typesetting, I also found the following bug: If I invoke Zoom, either with a key command or by clicking on the green button in the upper left corner of a window, Mission Control awakens and moves the window onto a different level. The menu bar disappears, too. I disabled Mission Control ages ago, and never use it. I disabled it again via the terminal after installing Yosemite. But this "ghost" connection remains. I can enlarge a window by manually dragging a corner without encountering this bug.
Jenny
When i open TextMate is always open a blank file called 'untitled'. Is there a way to prevent this blank file being generated when opening TextMate? Therefore can I open TextMate without without any file being opened?
Ross
In Finder to create a folder one would use ⌘⇧N, but in TextMate ⌘⌃N . Why the difference?
I’m always getting confused.
Why not using ⌘⇧N to create a folder and ⌘⌃N to create a file?
I use the Open Terminal command in the Shell Script bundle to automate LaTeXing of files. When I give this command (Control Shift O), whether Terminal.app is open or not, a tab is correctly open in Terminal in the right directory for my LaTeX file, but when the focus is back in TextMate, a Go to File (command T) has also opened. How can I avoid this? I can see the following lines in the Shell Script Open Terminal command but don't know how to prevent the opening of the Go to File window:
tell application "System Events"
tell process "Terminal" to keystroke "t" using command down
end tell
Thanks in advance for any pointer.
--gildas
Greetings,
I am running Beta3 with Yosemite and have issues with the latex bundle.
First, I have it configured to use pdflatex and open in Skim while displaying the command output in a separate window.
When I “Typeset and View” (CMD-R), it takes upwards of 5 seconds for anything to happen on a core i7 macbook pro (it initially brought up a dialog stating it was searching for Ruby 1.8, which took about 20-25 secs). Once the command output window appears, everything happens as normal very quickly with the final document appearing in Skim.
If I close Skim, close the command output window, then press CMD-R again, it still takes 4-5 seconds to begin before generating the document. If I close the command output window more than 2 two times, the next time I bring TextMate to the front, it will crash. It states that it is submitting the crash reports, but I can submit one of them to Allan directly if he desires (see main snippet below).
Anyone else have problems with the latex bundle: slow response and crashing TextMate?
Thanks,
Brian
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Application Specific Information:
Key equivalent ‘@w’.
Performing @selector(_close:) from sender _NSThemeCloseWidget 0x608000389240
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
Theres a feature in TM to automatically keep bundles updated
How does this work exactly?
Is it just for the default bundles, and theres some web service on the TM
website?
I'm wondering if I can hook into it somehow and have my third party
git-based bundles updated also
Thanks
Hello,
building latest textmate after a long time, I am hitting this error:
$ ninja TextMate
[9/36] Run test ‘/Users/dusek/build/TextMate/Frameworks/network/test_network’…
FAILED: /Users/dusek/build/TextMate/Frameworks/network/test_network && touch /Users/dusek/build/TextMate/Frameworks/network/test_network.run
test_network: 1 of 1 test failed:
/Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/network/tests/t_download.cc:58: Expected (network::download(network::request_t(url, &myFilter, NULL), &error) == 200), found (0 != 200)
[9/36] Run test ‘/Users/dusek/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate’…
FAILED: /Users/dusek/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate && touch /Users/dusek/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate.run
test_SoftwareUpdate: 5 of 6 tests failed:
/Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:64: Expected (err == "Extracting archive."), found ("Failed to connect to localhost port 64762: Connection refused" != "Extracting archive.")
/Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:73: Expected (err == "Extracting archive."), found ("Failed to connect to localhost port 64762: Connection refused" != "Extracting archive.")
/Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:82: Expected (err == "Bad signature."), found ("Failed to connect to localhost port 64762: Connection refused" != "Bad signature.")
/Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:91: Expected (err == "Bad signature."), found ("Failed to connect to localhost port 64762: Connection refused" != "Bad signature.")
/Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:109: Expected (err == NULL_STR), found ("Failed to connect to localhost port 64762: Connection refused" != "")
ninja: build stopped: subcommand failed.
I tried ninja network/coerce and ninja SoftwareUpdate/coerce and they do skip the relevant tests, but these choices do not persist and after running ninja TextMate again, I hit the same failures.
System: Xcode 6.0.1 (i.e. 10.9 SDK) running on Yosemite DP8 (14A361c), happens even on a totally clean rebuild (git clean -xffd; git reset --hard HEAD; rm -rf ~/build/TextMate/; ./configure && ninja)
Is there please anything I can do to make TextMate compile?
Thanks,
Boris
OS X has support for auto save and reverting to older file versions since Lion.
Are there any plans to support this in TextMate?
Is it hard to implement or there’s some other reason why it’s not supported?
Maybe it’s just not on the priority list?
Thanks.
