I hope you don't actually make this change... atomic save is desirable, even if you
end up losing some metadata.
What are other tools doing? I wonder if you give TM Full Disk Access, does it still throw
I think the below is a bad example, one that's promoted (unfortunately) by Outlook on
Windows. You shouldn't (IMO) assume that an attachment is something you can open and
write to and save again. If you want to save it, then you should be saving it somewhere
other than in the original message. Anything else just leads to eventual data loss and TM
shouldn't bend over backwards to facilitate it.
On Wed, Apr 15, 2020, at 7:24 PM, Allan Odgaard wrote:
On 16 Nov 2019, at 22:16, Timothy Bates wrote:
> Opened a file from an email attachment
> On save from textmate, I get this error:
> The document “BadFactorScoresExample.R”
could not be saved.
Apple Mail saves attachments in a Mail Downloads
folder that appears to be setup not to be writable (by other applications?).
It’s unclear to me how exactly it is setup, because
the classic file mode flags do allow writing, but try command-click the proxy icon, and
the folders are badged with a minus symbol:
This could be by design, because really, only Mail
should control those folders.
That said, you can disable atomic saving for all but
remote volumes by putting this in `~/.tm_properties`:
`atomicSave = remoteVolumes
This will make it work because TextMate then doesn’t
write a new file, but opens the existing file for (over)writing.
I’m considering making this the default, because with
the loss of `exchangedata` (when we moved to APFS) I think there are now too many
downsides to atomic saving to make it the default :(
> TextMate mailing list
> * PastedImage.png