Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Dave Korn" To: Subject: RE: unable to edit/less dotted files, etc. Date: Tue, 19 Oct 2004 18:30:31 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <41754575.1060908@barnlea.com> Message-ID: X-OriginalArrivalTime: 19 Oct 2004 17:30:31.0484 (UTC) FILETIME=[55422FC0:01C4B601] > -----Original Message----- > From: cygwin-owner On Behalf Of Julian Opificius > Sent: 19 October 2004 17:49 > I'm running v1.3 of Cygwin on Win2k on a laptop. That is _years_ out of date. > after the initial install, only later. I can list them with > ls -al, but > "vi .bashrc" opens up a new file, and less returns "No such file or > directory". The files are accessible under Win2k, and do not appear > corrupted. You've probably done something bad with the perms. Or you installed cygwin "Just for me", and now you've logged on as a different user.......? The "file not found" error message can often be a result of an application not realising that the file is there but the user doesn't have access rights. > Also, I now notice that other files - filenames that don't conform to > DOS 8.3 format - also are listable but not editable. I have a source > file "main.cas", which I can edit. I cp'd it to > "main_inst.cas", which > is listable with ls. But when I try to vi it, I get a new > file. mv'ing > it to maininst.cas renders it editable. Strange. Still, there's not a lot of point reporting bugs in such an old version of cygwin. I can't reproduce anything like that with the current version. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/