X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andy Subject: Re: Divergent file system contents, Cygwin versus Windows 7 Date: Sun, 26 Jun 2011 23:18:40 +0000 (UTC) Lines: 34 Message-ID: References: <4E079B14 DOT 2020800 AT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Daniel Colascione gmail.com> writes: > > On 6/26/11 11:37 AM, Andy wrote: > > I achieved the desired effect of modifying the nonvirtualized > > _vimrc by clicking on Compatibility Files to go to the > > virtualization directory and moving it from there to the location > > ov the nonvirtualized _vimrc (thus overwriting it). > > I usually run with UAC virtualization turned off, and I've > experienced no ill effects. You can turn off the virtualization > settings by disabling the "Windows Settings->Security > Settings->Local Policies->Security Options->UAC: Virtualize file and > registry write failures to per-user locations" option. See > http://technet.microsoft.com/en-us/library/dd851895.aspx > > That said, it's absolutely crazy that you're trying to write to a > vimrc in program files! Do you edit random files in /usr to change > settings under other Unixish systems? The real problem here is > vim's, and it's better to not let UAC mask such problems. That's a very interesting switch. I don't know what the best practice is yet for that switch. Virtualization can hide incompatibilities with Win 7 UAC and allow those incompatibilities to perpetuate. I'll leave the switch on for now until I see whether an explicit best practice emerges. I like the idea of separating user and system files, like in unix. However, the the vimrc file in Program Files is the default vimrc. I do in fact want to modify the default vimrc so that no matter what account launches gvim, it will inherit those settings (unless they are overridden by a local vimrc). Since I am the only user of this machine, new user accounts will only be created for experimental reasons, or to generate default account settings for snafu-recovery purposes. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple