Igor,
OK, I will just accept the situation!
Thanks, Chee
Igor Pechtchanski wrote:
Chee,
'/bin/vi' is a Cygwin program, and uses Cygwin system calls to create and
write files. Thus, the permissions it gives to newly-created files are
consistent with the other Cygwin apps. 'gvim' is probably a pu
Chee,
'/bin/vi' is a Cygwin program, and uses Cygwin system calls to create and
write files. Thus, the permissions it gives to newly-created files are
consistent with the other Cygwin apps. 'gvim' is probably a pure Windows
program, which uses the Windows API calls directly, so it gives new file
Dear Igor,
I guest there were no improvements on the execute permission problem.
But I just realized that "vi" under cygwin is smart enough
not to give execute permissions to the files it writes
out. It simply keep the original permissions. Why can't gvim
do the same?
Best,
--Chee
Igor Pechtchan
Chee,
Well, there are people on this list who are more versed in Windows
permissions issues than I, and hopefully they'll intervene and either
confirm or refute my answer. If I had to guess, I'd say this has to do
with inheritable permissions -- if a directory has an execute permission
and the fl
Dear Igor,
Nice to hear from you, and thanks for the clarification!
I understand your explanation of the difference between
gvim and vim. But there is still a mystery.
In my previous installation of cygwin, no such problems
arise. The difference is that my previous system was Windows 2000
and my
On Tue, 30 Sep 2003, Yap on ExactGeom wrote:
> Dear Igor,
>
> How are you? I noticed that you are an active developer of cygwin.
> I really liked this platform and our Core Library is developed
> on this mainly. I have a question:
>
> In my recent (June) installation of cygwin, there was an ann
6 matches
Mail list logo
