TextMate 2 beta 3 seems to be crashing after compiling latex code a couple
of times after upgrading to Yosemite. I've tried a few different latex
files, which worked before Yosemite. I compile two or three times, and
Textmate closes and sends a crash report:
I'm on TeXlive 2014, but this happened before upgrading from TeXlive 2013.
Would anyone know what is going on?
> On Oct 31, 2014, at 1:37 AM, textmate-request(a)lists.macromates.com wrote:
> From: "Allan Odgaard" <mailinglist(a)textmate.org <mailto:firstname.lastname@example.org>>
> To: "TextMate users" <textmate(a)lists.macromates.com <mailto:email@example.com>>
> Subject: [TxMt] Re: Lost file when didn't have permission to write.
> Message-ID: <8589BDAC-685B-4CAD-9327-382E352F7C47(a)textmate.org <mailto:8589BDAC-685B-4CAD-9327-382E352F7C47@textmate.org>>
> Content-Type: text/plain; charset=utf-8; format=flowed
> On 31 Oct 2014, at 1:03, Greg wrote:
>> I?m writing Ruby scripts for a Raspberry Pi (RPi) using TextMate
>> v2.0-beta.1. The RPi is on my network and I?m accessing the files
>> via Transmit (OS X FTP GUI program). From Transmit I open, edit and
>> save the files. However I just opened the ReadMe.tm created by GitHub,
>> did some editing, saved and closed. I hadn?t seen that I had
>> received a notice from Transmit that I didn?t have permissions to
>> modify the file, but the changes were gone (RPi is slow).
> TextMate tells Transmit that the file has closed, it does not remove it
> (this would be done by Transmit). It also does not know, that Transmit
> is unable to upload the file.
> So I don?t think TextMate can really do anything better here.
Afraid of that.
Thanks for responding.
Not sure if this is the right way to reply to a digest.