[obligatory thanks for a very useful application]
One common phase of my workflow is to audit source changes between built versions of a product. The sources for each build are archived in read-only folders on a network share.
When comparing two files in this situation, DiffMerge presents a dialog complaining that it "Failed to create a temporary file name (error 13: Permission denied)".
From a user's perspective, it would make sense for the compare to open in a read-only fashion (i.e. automatically applying the --ro2 option). The dialog is perhaps more intrusive and annoying than necessary to communicate that changes can't be made in the new window.
= Mike
[3.3.0, MacOS X] Temporary files and read-only directories
Moderator: SourceGear
-
- Posts: 3
- Joined: Fri Jun 19, 2009 4:08 pm
-
- Posts: 534
- Joined: Tue Jun 05, 2007 11:37 am
- Location: SourceGear
- Contact:
Re: [3.3.0, MacOS X] Temporary files and read-only directories
Good point. It should either sense that everything is read-only and force the --ro2 or
it should create the temp file in the platform-equivalent of /tmp or maybe both. But
if everything is read-only, it doesn't really need the temp file (it's only used for auto-save).
I've logged this.
Thanks for the report,
jeff
14497
it should create the temp file in the platform-equivalent of /tmp or maybe both. But
if everything is read-only, it doesn't really need the temp file (it's only used for auto-save).
I've logged this.
Thanks for the report,
jeff
14497