X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.9 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,SPF_HELO_PASS,TW_HK,TW_KD,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	JimE <jaeuvt AT gmail DOT com>
Subject:	Win/CygWin don't show the same file content!
Date:	Tue, 8 May 2012 13:31:45 +0000 (UTC)
Lines:	32
Message-ID:	<loom.20120508T152149-248@post.gmane.org>
Mime-Version:	1.0
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:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Hi All!
   I have used Cygwin on XP for years don't know what I'd do without it - thanks
to everybody who help make Cygwin available!

   I changed over to Windows 7 in the last 6 months or so, and have twice run in
to an issue where listing/cat'ing files under Cygwin has different results than
under Windows.

   The first time, I edited a text file with emacs in Cygwin.  When the Windows
EXE file I was working on read that file, it only saw the old results.   I used
windows to navigate to the same directory and found the old results when I used
Notepad, Wordpad, or Visual Studio.   Using Emacs or "cat" in Cygwin showed me
the new file data.   
   I believe that I also saw the new file data using a Windows version of emacs,
though I'm not 100% positive.

   A reboot with a check disk ( took a _long_ time ) seemed to clear up this issue.


   Yesterday I ran in to a similar problem.   I used Windows explorer to rename
files in a directory, but when I used "ls" under Cygwin I saw the old file names.
   Again, a reboot with chkdsk seemed to fix the problem.


   Has anybody seen something like this before?   What can I do to avoid this in
the future?


   Thanks!

JimE



--
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

- Raw text -