From: Chris Faylor <cgf@cygnus.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: Cygwin performance (was [ANN] PW32 the...)
Date: Thu, 16 Mar 2000 10:22:00 -0000 [thread overview]
Message-ID: <20000316132145.A25190@cygnus.com> (raw)
In-Reply-To: <20000316173203.853C91F1F@sabami.seaslug.org>
On Thu, Mar 16, 2000 at 09:32:03AM -0800, Scott Blachowicz wrote:
>Heribert Dahms <heribert_dahms@icon-gmbh.de> wrote:
>> are you hardwired to 'ls', 'ls -l' or (like me) 'll'?
>> My stock b20 'ls' spits out only filenames!
>
>I usually use 'ls -l', but what I really want (usually) is the filenames,
>sizes and mod times (and sometimes permissions). And, if I want that, I'll
>have to take the stat() penalty, I guess. So...I was curious...what is it in
>the stat() call that can only be obtained by opening the file? Is it just the
>cygnus stat() emulation that does that? One of these days, maybe I'll try out
>a native-Win32 perl 'ls' wrapper script...
The Windows API dictates that much of the information required to fill in a
stat structure can only come by querying an open file handle.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-03-16 10:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 13:43 Heribert Dahms
2000-03-15 14:01 ` Larry Hall (RFK Partners, Inc)
2000-03-16 9:32 ` Scott Blachowicz
2000-03-16 10:22 ` Chris Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-16 10:26 Chris Nappi
2000-03-16 10:43 ` Larry Hall (RFK Partners, Inc)
2000-03-13 10:04 [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released Earnie Boyd
2000-03-13 11:21 ` Re[2]: " Paul Sokolovsky
2000-03-13 15:16 ` Larry Hall (RFK Partners, Inc)
2000-03-13 15:56 ` Chris Faylor
2000-03-13 16:23 ` Jeff Sturm
2000-03-13 18:08 ` Cygwin performance (was [ANN] PW32 the...) Geoffrey Noer
2000-03-14 16:29 ` Scott Blachowicz
2000-03-14 21:04 ` Chris Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000316132145.A25190@cygnus.com \
--to=cgf@cygnus.com \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).