delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT sources DOT redhat DOT com |
Delivered-To: | mailing list cygwin AT sources DOT redhat DOT com |
X-Lotus-FromDomain: | JPMORGAN AT SMTP |
From: | "Noel L Yap" <yap_noel AT jpmorgan DOT com> |
To: | cygwin AT sourceware DOT cygnus DOT com |
Message-ID: | <85256929.0079F944.00@nyc-ntgw-n01.ny.jpmorgan.com> |
Date: | Thu, 27 Jul 2000 18:12:21 -0400 |
Subject: | can't vi a file (sometimes) |
Mime-Version: | 1.0 |
I've reported this problem before but I wasn't sure if it was something other than vi (that comes with Cygwin). The problem: vi .bash/.bash_set # gets a "Permission Denied" for the file .bash/.bash_set However: cd .bash vi .bash_set # works perfectly And: xemacs .bash/.bash_set # works perfectly, too So, barring something I've missed, the problem must lie within 'vi' itself. Noel This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its subsidiaries and affiliates. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |