Thank you and thank you!

So it sounds like it's not any one of the products I'm using, but the way they interact. TextMate opens a local copy that Transmit creates, and, it seems that when I save in TextMate, TextMate sends the metadata, and Transmit respects that and saves it to the server. But since I've changed the permissions in the interim, my changes on the server (outside TextMate and Transmit) are being lost as a result.

I will have to change the way I work with that, so that I change permissions first and then open it in TextMate via Transmit in the future.

I'll also look into rmate, but not sure that will work for me either...


On Tue, Jul 9, 2013 at 1:33 PM, Jason Smith <> wrote:
Caveat: rmate now requires permission to install python gems on the target server, instead of the previously minimally invasive script that could be simply plopped into ~/bin

This has drastically curtailed my ability to use rmate remotely.


On Jul 9, 2013, at 13:18, "Allan Odgaard" <> wrote:

> On 9 Jul 2013, at 16:45, Jeff Weinberger wrote:
>> [] If TextMate re-writes the file with the metadata from the time it was
>> originally opened, then that would cause the issue. If it writes the file
>> without changing the then-current metadata (which have changed since it was
>> opened) then the issue is likely Transmit.
> TextMate works on a temporary file that Transmit created and knows nothing about the file on your server.
> If you change the file on the server while it is open in TextMate, then it would fall upon Transmit to sync the changes when TextMate saves and triggers Transmit to upload the (temporary) file.
> Are you btw aware of rmate? If you work a lot over ssh, then rmate is a great asset, and when rmate accepts changes from TextMate, it will preserve metadata :)
> _______________________________________________
> textmate mailing list

textmate mailing list