From: "Hannu E K Nevalainen" <garbage_collector@telia.com>
To: <cygwin@cygwin.com>
Subject: RE: bash /usr/bin/ls invalid argument
Date: Tue, 28 Oct 2003 12:57:00 -0000 [thread overview]
Message-ID: <NGBBLLIAMFLGJEOAJCCEKEMODFAA.garbage_collector@telia.com> (raw)
In-Reply-To: <4FF77D01E13B214590F4FA3E2C3021D0873ADA@pecos.csw.alewife.net>
> From: Jared Ingersoll
> Sent: Monday, October 27, 2003 8:55 PM
> I'm using bash 2.05b-16 on Win2K pro and I'm running into problems listing
> directory contents with a wildcard. This particular directory has
> over 8000
> files in it, most of which (99%) are files that start with
> send.log.*. When
> I issue the following commands, I get the same error:
>
> $ ls send.log.*
> bash: /usr/bin/ls: Invalid argument
For newbies: to get to grips about how this works "under the hood"; read up
on how "Shell expansion" works in e.g. bash (i.e. search and read the "man"
or "info" on bash)
IIRC there was a recent thread (about environment variables and passing
arguments to a windows-console program):
There is a 32KB length limit on the command line. This is imposed on us by
the underlying "OS" - i.e. not likely to change.
To check how long your command line would be, try something like this:
$ find -type f -name 'send.log.*' |
(
read f;
cc=-1;
echo "";
while [ ! -z "$f" ];do
cc=$(( 1 + $cc + $( echo "$f" | wc -c) ));
echo -e "\e[F$cc\e[K";read f;
done;
echo -e "\e[F$cc chars"
)
Remember to add the length of e.g. "ls -l " (note space).
If this gives a number larger than...
$ echo $(( ( 1 << 15 ) -1 ))
32767
... then you're "outta luck".
/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- printf("Timezone: %s\n", (DST)?"UTC+02":"UTC+01"); --
--END OF MESSAGE--
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-10-28 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 0:12 Jared Ingersoll
2003-10-28 1:13 ` Andrew DeFaria
2003-10-28 12:57 ` Hannu E K Nevalainen [this message]
2003-10-29 10:17 ` Nicolas BUONOMO
2003-10-29 15:23 ` Hannu E K Nevalainen
2003-10-28 14:08 Jared Ingersoll
2003-10-28 16:05 ` Christopher 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=NGBBLLIAMFLGJEOAJCCEKEMODFAA.garbage_collector@telia.com \
--to=garbage_collector@telia.com \
--cc=cygwin@cygwin.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).