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:	michael-ring AT t-online DOT de
cc:	cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<8525691F.004650BA.00@nyc-ntgw-n01.ny.jpmorgan.com>
Date:	Mon, 17 Jul 2000 08:48:05 -0400
Subject:	Re: vi Permission Denied problems
Mime-Version:	1.0

Everything seems to check out the same as your setup except that I have /home
mounted (ie Cygwin mounted) to a drive that's mapped to a network drive.  Thanks
for your help, though -- I hadn't realised I stomped my EDITOR definition.

Noel




michael-ring AT t-online DOT de on 2000.07.15 03:27:10

To:   yap_noel AT jpmorgan DOT com
cc:
Subject:  Re: vi Permission Denied problems




On Fri, 14 Jul 2000 12:17:08 -0400, you wrote:
>
>Here's what happens:
>> vi .bash/.bash_set
># vi is unable to open the file due to a "Permission Denied" problem
>> vi ./.bash/.bash_set
># same problem
>> vi ~/.bash/.bash_set
># this works perfectly
>
>Anyone have any idea as to what's going on?
>

My environment is close to your's, I am also mounting $HOME from
somewhere else (In my case linux box with samba). I have tested all
three versions and they all worked. Then I thought it could perhaps be
something that pops up if /home/$USER is mounted but the directory
/home/$USER is not existant. But that also worked fine on my
installation (1.1.2).

The only thing that might perhaps be a hint is the following:

I saw that EDITOR=/vi is set in your environment. If you use the
installation of vim-5.7 from latest (which I am using) then vi is
/bin/vi. perhaps you have two vi's (or another version of vi) on your
machine. In that case you shoud think about updating.

try a <ESC>:version inside of vi. the result should be something like
that:

VIM - Vi IMproved 5.7 (2000 Jun 24, compiled Jul 11 2000 14:08:36)
Compiled by ring AT BOWMAN, with (+) or without (-):
+autocmd -browse ++builtin_terms +byte_offset +cindent +cmdline_compl
+cmdline_info +comments +cryptv +cscope +dialog_con +digraphs
+emacs_tags +eval
+ex_extra +extra_search +farsi +file_in_path -osfiletype +find_in_path
+fork()
-GUI -hangul_input +insert_expand +langmap +linebreak +lispindent
+menu
+mksession +modify_fname +mouse +mouse_dec -mouse_gpm +mouse_netterm
+mouse_xterm +multi_byte -perl -python +quickfix +rightleft
+scrollbind
+smartindent -sniff +statusline +syntax +tag_binary +tag_old_static
-tag_any_white -tcl -terminfo +textobjects +title +user_commands
+visualextra
+viminfo +wildignore +wildmenu +writebackup -X11 -xfontset -xim
-xterm_clipboard -xterm_save
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -g -O2 -Wall
Linking: gcc  -o vim         -ltermcap  /usr/lib/textmode.o

>Thanks,
>Noel
>
>Enc
>(See attached file: cygcheck.out)

I hope that helped

Michael Ring





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

- Raw text -