Hi,
I would like to disable the automatic file backup in TM. I didn't find an option in the preferences menu - could someone please tell me how to do this?
THX,
Andreas
On Apr 2, 2006, at 11:38 PM, Andreas Biegert wrote:
I would like to disable the automatic file backup in TM. I didn't find an option in the preferences menu - could someone please tell me how to do this?
I didn't even know TM had automatic file backup in the first place. How exactly is TM backing up your files?
Trevor
Andreas: are you referring to this?
Preferences -> Advanced -> Saving Tab -> Other: Save files when focus is lost
Not really the same as automatic backup, but I thought this might be what you were talking about.
-Brad
On Apr 3, 2006, at 12:10 AM, Trevor Harmon wrote:
On Apr 2, 2006, at 11:38 PM, Andreas Biegert wrote:
I would like to disable the automatic file backup in TM. I didn't find an option in the preferences menu - could someone please tell me how to do this?
I didn't even know TM had automatic file backup in the first place. How exactly is TM backing up your files?
Trevor
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
I am not sure if it solves my problem but I will try it. My coworkers (all emacs users) were complaining about .filename files that TM seems to create as autobackup.
-Andreas
2006/4/3, Brad Choate bchoate@gmail.com:
Andreas: are you referring to this?
Preferences -> Advanced -> Saving Tab -> Other: Save files whenfocus is lost
Not really the same as automatic backup, but I thought this might be what you were talking about.
-Brad
On Apr 3, 2006, at 12:10 AM, Trevor Harmon wrote:
On Apr 2, 2006, at 11:38 PM, Andreas Biegert wrote:
I would like to disable the automatic file backup in TM. I didn't find an option in the preferences menu - could someone please tell me how to do this?
I didn't even know TM had automatic file backup in the first place. How exactly is TM backing up your files?
Trevor
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On 3/4/2006, at 9:39, Andreas Biegert wrote:
I am not sure if it solves my problem but I will try it. My coworkers (all emacs users) were complaining about .filename files that TM seems to create as autobackup.
That’s meta data:
http://macromates.com/textmate/manual/ saving_files#extended_attributes_metadata
On Apr 3, 2006, at 1:04 AM, Allan Odgaard wrote:
On 3/4/2006, at 9:39, Andreas Biegert wrote:
I am not sure if it solves my problem but I will try it. My coworkers (all emacs users) were complaining about .filename files that TM seems to create as autobackup.
That’s meta data:
http://macromates.com/textmate/manual/ saving_files#extended_attributes_metadata
Ah, yes, I've had this problem when using TextMate to edit files mounted remotely on a Linux server. TM leaves tiny binary files scattered all over the place. (They're all prefixed with ":2e_", so they're not hidden, which makes this problem especially annoying.)
Are there any plans to make this metadata storage a project-specific option? I'd like to turn it off when working with my Linux project but leave it on for everything else.
Trevor
On 3/4/2006, at 10:24, Trevor Harmon wrote:
That’s meta data: http://macromates.com/textmate/manual/ saving_files#extended_attributes_metadata
Ah, yes, I've had this problem when using TextMate to edit files mounted remotely on a Linux server. TM leaves tiny binary files scattered all over the place. (They're all prefixed with ":2e_", so they're not hidden, which makes this problem especially annoying.)
That’s strange (the prefix). What type of file system is that? Does TM correctly read the files (i.e. are caret position etc. preserved when re-opening the file)?
Are there any plans to make this metadata storage a project- specific option? I'd like to turn it off when working with my Linux project but leave it on for everything else.
More likely a file system specific setting, as that would make more sense.
On Apr 3, 2006, at 12:12 PM, Allan Odgaard wrote:
Ah, yes, I've had this problem when using TextMate to edit files mounted remotely on a Linux server. TM leaves tiny binary files scattered all over the place. (They're all prefixed with ":2e_", so they're not hidden, which makes this problem especially annoying.)
That’s strange (the prefix). What type of file system is that?
The remote Linux server is ext3, but I've got it mounted remotely via the Netatalk implementation of the Apple Filing Protocol. I suspect that's what's causing periods to be converted to :2e.
Does TM correctly read the files (i.e. are caret position etc. preserved when re-opening the file)?
Yes.
Are there any plans to make this metadata storage a project- specific option? I'd like to turn it off when working with my Linux project but leave it on for everything else.
More likely a file system specific setting, as that would make more sense.
Hmm, would that actually solve the problem in my case? That is, it appears to be an issue with the mount protocol, not the actual file system.
Trevor
On 4/4/2006, at 0:30, Trevor Harmon wrote:
More likely a file system specific setting, as that would make more sense.
Hmm, would that actually solve the problem in my case? That is, it appears to be an issue with the mount protocol, not the actual file system.
But the file system is unlikely going to report itself as hfs. Try change the path below to a file on your mounted remote file system and paste it in Terminal:
gcc -x c <<EOF - && ./a.out #include <sys/mount.h> main () { struct statfs sfsb; statfs("/Volumes/Macintosh HD", &sfsb); puts(sfsb.f_fstypename); } EOF
You may want to “rm a.out” afterwards.
On Apr 3, 2006, at 3:42 PM, Allan Odgaard wrote:
On 4/4/2006, at 0:30, Trevor Harmon wrote:
More likely a file system specific setting, as that would make more sense.
Hmm, would that actually solve the problem in my case? That is, it appears to be an issue with the mount protocol, not the actual file system.
But the file system is unlikely going to report itself as hfs. Try change the path below to a file on your mounted remote file system and paste it in Terminal:
You're right; it reports "afpfs". But this problem could just be a bug in Netatalk, and "real" AFP volumes work fine. So a per-project setting might still be desirable.
Trevor
On 4/4/2006, at 7:52, Trevor Harmon wrote:
You're right; it reports "afpfs". But this problem could just be a bug in Netatalk, and "real" AFP volumes work fine. So a per-project setting might still be desirable.
Have you considered reporting the bug with the maintainers of Netatalk?
On Apr 4, 2006, at 12:33 AM, Allan Odgaard wrote:
On 4/4/2006, at 7:52, Trevor Harmon wrote:
You're right; it reports "afpfs". But this problem could just be a bug in Netatalk, and "real" AFP volumes work fine. So a per- project setting might still be desirable.
Have you considered reporting the bug with the maintainers of Netatalk?
D'oh! I should learn to use Google before assuming something is a bug. Turns out that this hex encoding is a "feature" turned on by default to prevent illegal character conflicts between file systems. And there's a "usedots" option that turns off the conversion only for filenames with a leading period, which is what most people want. (Why this is not the default, I don't know.) See:
http://netatalk.sourceforge.net/2.0/htmldocs/AppleVolumes.default.5.html
So, problem solved!
Trevor
-
Allan Odgaard -
Andreas Biegert -
Brad Choate -
Trevor Harmon