On Wed, 05 Mar 2014 19:10:32 +0100 Jonas Bernoulli <[email protected]> wrote:
JB> So there is the option `magit-turn-on-auto-revert-mode' and you are JB> arguing it should default to nil. You didn't find this option on your JB> own even though you knew the relevant term was "auto-revert" and could JB> have grepped the source for it. I'm not asking to change the default for `magit-turn-on-auto-revert-mode', but that Magit shouldn't be enabling a global mode with the potential to lose data when it's *loaded*. The mechanics are not important. In my case, to determine Magit was the problem, I had to turn off packages one by one. I didn't *know* `auto-revert-mode' was on and actually lost work because of it. That didn't happen before the change you mention, I'm positive. I've been a Magit user for a while. JB> So I think that keeping this turned on is an acceptable compromise for JB> the time being, considering that this only has an effect in git JB> repositories. Sure magit might not be "used", but how would you check JB> whether magit is in used? To me, `M-x magit' seems the right indicator that Magit is used, so I'd add to the file hook there. Ted -- You received this message because you are subscribed to the Google Groups "magit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
