Wendell Pinegar wrote:
The MKS Toolkit for instance does properly ignore these file types.
Not surprising. The goals of the two products are somewhat different.
MKS is trying to make their environment look exactly like the native
Windows. They have written most of their tools from scratch to
Wendell Pinegar [EMAIL PROTECTED] wrote:
There seems to be a long running defect in the implementation of
ls.exe. It shows windows system hidden files - which it shouldn't do
by default. On Unix systems files are hidden by placing a period in
front of the filename (ie, .profile), but in the
Wendell,
That is at the very best a matter of opinion and I don't think your opinion
is widely shared. In particular, the mixing of file system models in the
ls source code that would be required to implement your suggestion would
render ls a horse of a different color and would set a poor
shows windows system hidden files
Wendell Pinegar [EMAIL PROTECTED] wrote:
There seems to be a long running defect in the implementation of
ls.exe. It shows windows system hidden files - which it shouldn't do
by default. On Unix systems files are hidden by placing a period in
front
Hi,
Perhaps a utility analogous to getfacl and setfacl for Windows-specific
file system properties is in order. If done properly, it could be used by
those few who need to restrict output of other commands w.r.t. to Windows
properties not otherwise accessible in Cygwin.
Randall Schulz
:
-
From: Wendell Pinegar [EMAIL PROTECTED]
Date: Mon, 2 Dec 2002 15:09:02 -0600
To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: RE: ls.exe shows windows system hidden files
In our instance the reason this an issue is that we call the ls.exe utility
from PHP web code
[EMAIL PROTECTED] wrote:
Hi,
Try to remember that cygwin is a unix emulation layer for windows that
tries to emulate unix in as many respects as possible. To change the
ls source to accomadate for something windows uses to hide files,
sometimes unknown from its users, would not be unix like.
On Mon, Dec 02, 2002 at 01:39:58PM -0800, Randall R Schulz wrote:
Perhaps a utility analogous to getfacl and setfacl for
Windows-specific file system properties is in order. If done properly,
it could be used by those few who need to restrict output of other
commands w.r.t. to Windows properties
Chris,
I suppose that would be an adequate basis for constructing something with
the effect I imagined.
Realistically, if I cared about being able to do this, I'd probably wrap
the Windows attrib command in a script that would allow it to accept
Cygwin's POSIX paths and to allow it to act
Andrew,
Cygwin uses stock ls source code. Cygwin's ps is entirely it's
own--it's all distinctly Cygwin.
I still think an orthogonal approach is what's called for here. Otherwise,
the number of commands that could reasonably be expected to have this sort
of functionality would be much to large
Randall R Schulz wrote:
Andrew,
Cygwin uses stock ls source code. Cygwin's ps is entirely it's
own--it's all distinctly Cygwin.
Makes sense.
Still I would like ls to do it (in my case by default). You see I'm one
of those, I guess, few Windows users who actually uses hidden files and
11 matches
Mail list logo
