X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 26 Jun 2011 11:20:39 -0400 Message-ID: Subject: Re: Windows 7? Two different versions of a file depending on how it is accessed From: Andrew Hancock To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p5QFKvEY032491 Sorry, this thread has been superseded by "Divergent file system contents, Cygwin versus Windows 7" (http://article.gmane.org/gmane.os.cygwin/127335).  During the thick of troubleshooting, I lost track of the fact that I posted this earlier understanding of the problem. On Sun, Jun 26, 2011 at 10:40 AM, Andrew Hancock wrote: > I am seeing two different versions of a file depending on how I access > it.  Specifically, the file "C:\Program Files (x86)\Vim\_vimrc" uses > plain text to provide startup specifications for the text editor gvim. >  This is the standalone installation for Windows, not the one the one > that comes with Cygwin.  However, that is just the problem context. > The real issue is that I see two different versions of that file.  The > first version is the original one that came with the installation.  I > modified it by adding the lines: > >   set guioptions-=m >   set guioptions-=T > > I got a warning that the file is read-only.  It isn't according > read-only to "ls -l", but I thought that the discrepancy must have > been due to Windows 7's more complicated security (which I haven't > completely figured out).  I forced the save with "w!", tested it by > restarting gvim, and found that the settings did not take.  I wondered > whether the file actually contained the above two lines that I added. > > It turns out that it depends on how the file is accessed.  If I access > the file using notepad or windows-based gvim, the two added lines are > not present (same thing if I use Windows's "more" from cmd.exe).  On > the other hand, if I access the file using vim or less from cygwin's > bash shell, the two added lines *are* present.  After googling about > different versions of files on Windows 7, I found that one possible > cause might be the backups that the OS makes.  However, I confirmed > that this particular file has no backups. > > Right now, I am not sure whether this is a Windows 7 problem or a > cygwin problem (or more likely, an interaction between them).  Can > anyone suggest a next possible course of action?  I don't want to > force both copies to be the same by simply editting the file using the > Windows-base gvim.  This hides a problem that will doubtlessly come > back and cause great grief. > -- 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