Filename globbing/wildcards

Filename globbing/wildcards

[Derwin, Frank]

Hi,

I've just started using the 1.0 Cygwin CD release.

I have a problem with filename globbing.  A single * expands correctly to
give all filenames.

But any variation on this (such as a* or *a) gives the error "Filename too
long", whether or not there are files that match the pattern.

Any suggestions?

Frank Derwin                             

Systems Services
FISC-Ireland
speed dial:  8 737 5475
external   : +353 1 614 5475

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Filename globbing/wildcards

[Chris Faylor]

On Wed, Jul 26, 2000 at 09:48:34AM +0100, Derwin, Frank wrote:
>I've just started using the 1.0 Cygwin CD release.
>
>I have a problem with filename globbing.  A single * expands correctly to
>give all filenames.
>
>But any variation on this (such as a* or *a) gives the error "Filename too
>long", whether or not there are files that match the pattern.
>
>Any suggestions?

I can't duplicate this behavior.  Sorry.

Are you doing this from a command shell?  From bash?  What command are you
using?

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Filename globbing/wildcards

[Chris Faylor]

On Wed, Jul 26, 2000 at 10:11:38AM -0700, Earnie Boyd wrote:
>You're welcome.  Are you using the shortcut to the cygwin.bat file?  Did you
>modify this file?  I'm asking because the setup process is supposed to put the
>path to cygwin first in PATH.  But, only if you're using the cygwin.bat file.

There is no cygwin.bat on the Cygwin CD, unfortunately.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Filename globbing/wildcards

[Earnie Boyd]

--- "Derwin, Frank" <Frank.Derwin@fid-intl.com> wrote:
> I solved the problem.  The NT Resource Kit was earlier in the path than
> cygwin!
> 
> Thanks for your help.
> 

You're welcome.  Are you using the shortcut to the cygwin.bat file?  Did you
modify this file?  I'm asking because the setup process is supposed to put the
path to cygwin first in PATH.  But, only if you're using the cygwin.bat file.

Cheers,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Filename globbing/wildcards

[Noel L Yap]

Yes: echo M*

Noel




mminnis@prefres.com on 2000.07.26 11:55:20

To:   cygwin@sources.redhat.com
cc:   (bcc: Noel L Yap)
Subject:  Re: Filename globbing/wildcards




This brings up an interesting question.....  :)

Is there a way/utility in Cygwin to view the output of what a certain
wildcard expansion would return?

Like M*

sh> utility_name M*

Returns to stdout (or file):
Mark
Matt
Matilda
Melvin
...



Thanks,

Matt


At 10:51 AM 7/26/2000 -0400, Chris Faylor wrote:
>On Wed, Jul 26, 2000 at 03:03:06PM +0100, Derwin, Frank wrote:
> >I am doing a simple ls a* in a ksh script.
> >
> >I've tried it in the bash shell too and I get the same behaviour.
>
>Since the filename expansion for bash and ksh is done in the shells
>themselves, it's odd that you would be seeing the same behavior in
>both.
>
>A 'cygcheck -r -s -v' might help pinpoint your problem.
>
>cgf
>
> >> -----Original Message-----
> >> From:        Chris Faylor [SMTP:cgf@cygnus.com]
> >> Sent:        Wednesday, July 26, 2000 2:53 PM
> >> To:  'cygwin@sourceware.cygnus.com'
> >> Cc:  Frank.Derwin@fid-intl.com
> >> Subject:     Re: Filename globbing/wildcards
> >>
> >> On Wed, Jul 26, 2000 at 09:48:34AM +0100, Derwin, Frank wrote:
> >> >I've just started using the 1.0 Cygwin CD release.
> >> >
> >> >I have a problem with filename globbing.  A single * expands correctly to
> >> >give all filenames.
> >> >
> >> >But any variation on this (such as a* or *a) gives the error "Filename
> >> too
> >> >long", whether or not there are files that match the pattern.
> >> >
> >> >Any suggestions?
> >>
> >> I can't duplicate this behavior.  Sorry.
> >>
> >> Are you doing this from a command shell?  From bash?  What command are you
> >> using?
> >>
> >> cgf
> >
> >--
> >Want to unsubscribe from this list?
> >Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>--
>cgf@cygnus.com                        Cygnus Solutions, a Red Hat company
> http://sourceware.cygnus.com/         http://www.redhat.com/
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Cthulhu for President. Why settle for a lesser evil?

=========================================================
Preferred Resources          (314) 567-7600 phone
701 Emerson rd.              (314) 993-6699 fax
Suite 475             mminnis@prefres.com
St. Louis, MO
63141
=========================================================


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com






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@sourceware.cygnus.com

RE: Filename globbing/wildcards

[Derwin, Frank]

I solved the problem.  The NT Resource Kit was earlier in the path than
cygwin!

Thanks for your help.


> -----Original Message-----
> From:	Earnie Boyd [SMTP:earnie_boyd@yahoo.com]
> Sent:	Wednesday, July 26, 2000 3:27 PM
> To:	Derwin, Frank; 'cygwin@sourceware.cygnus.com'
> Subject:	Re: Filename globbing/wildcards
> 
> --- "Derwin, Frank" <Frank.Derwin@fid-intl.com> wrote:
> > Hi,
> > 
> > I've just started using the 1.0 Cygwin CD release.
> > 
> > I have a problem with filename globbing.  A single * expands correctly
> to
> > give all filenames.
> > 
> > But any variation on this (such as a* or *a) gives the error "Filename
> too
> > long", whether or not there are files that match the pattern.
> > 
> > Any suggestions?
> > 
> 
> I've a few but I don't know which one fits.  Exactly what is the command
> you're
> using when you see this error?  What shell interpreter are you using?
> Paste
> the output of `cygcheck -v -r -s' in your response to the list, not to me.
> 
> Regards,
> 
> =====
> ---
>    Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
>             __Cygwin: POSIX on Windows__
> Cygwin Newbies: < http://gw32.freeyellow.com/ >
>            __Minimalist GNU for Windows__
>   Mingw32 List: < http://www.egroups.com/group/mingw32/ >
>     Mingw Home: < http://www.mingw.org/ >
> 
> __________________________________________________
> Do You Yahoo!?
> Get Yahoo! Mail - Free email you can access from anywhere!
> http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Filename globbing/wildcards

[Bob McGowan]

"Richard Hellicar (EML)" wrote:
> 
> ls -1d M*

Note that -ld above is the number 'one' followed by the letter 'd'.

Or:
	echo M* # one line, names separated by spaces

> > This brings up an interesting question.....  :)
> >
> > Is there a way/utility in Cygwin to view the output of what a certain
> > wildcard expansion would return?
> >
> > Like M*
> >
> > sh> utility_name M*
> >
> > Returns to stdout (or file):
> > Mark
> > Matt
> > Matilda
> > Melvin
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan@veritas.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Filename globbing/wildcards

[Richard Hellicar (EML)]

ls -1d M*

> This brings up an interesting question.....  :)
> 
> Is there a way/utility in Cygwin to view the output of what a certain 
> wildcard expansion would return?
> 
> Like M*
> 
> sh> utility_name M*
> 
> Returns to stdout (or file):
> Mark
> Matt
> Matilda
> Melvin


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Filename globbing/wildcards

[Matt Minnis]

This brings up an interesting question.....  :)

Is there a way/utility in Cygwin to view the output of what a certain 
wildcard expansion would return?

Like M*

sh> utility_name M*

Returns to stdout (or file):
Mark
Matt
Matilda
Melvin
...



Thanks,

Matt


At 10:51 AM 7/26/2000 -0400, Chris Faylor wrote:
>On Wed, Jul 26, 2000 at 03:03:06PM +0100, Derwin, Frank wrote:
> >I am doing a simple ls a* in a ksh script.
> >
> >I've tried it in the bash shell too and I get the same behaviour.
>
>Since the filename expansion for bash and ksh is done in the shells
>themselves, it's odd that you would be seeing the same behavior in
>both.
>
>A 'cygcheck -r -s -v' might help pinpoint your problem.
>
>cgf
>
> >> -----Original Message-----
> >> From:        Chris Faylor [SMTP:cgf@cygnus.com]
> >> Sent:        Wednesday, July 26, 2000 2:53 PM
> >> To:  'cygwin@sourceware.cygnus.com'
> >> Cc:  Frank.Derwin@fid-intl.com
> >> Subject:     Re: Filename globbing/wildcards
> >>
> >> On Wed, Jul 26, 2000 at 09:48:34AM +0100, Derwin, Frank wrote:
> >> >I've just started using the 1.0 Cygwin CD release.
> >> >
> >> >I have a problem with filename globbing.  A single * expands correctly to
> >> >give all filenames.
> >> >
> >> >But any variation on this (such as a* or *a) gives the error "Filename
> >> too
> >> >long", whether or not there are files that match the pattern.
> >> >
> >> >Any suggestions?
> >>
> >> I can't duplicate this behavior.  Sorry.
> >>
> >> Are you doing this from a command shell?  From bash?  What command are you
> >> using?
> >>
> >> cgf
> >
> >--
> >Want to unsubscribe from this list?
> >Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>--
>cgf@cygnus.com                        Cygnus Solutions, a Red Hat company
> http://sourceware.cygnus.com/         http://www.redhat.com/
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Cthulhu for President. Why settle for a lesser evil?

=========================================================
Preferred Resources          (314) 567-7600 phone
701 Emerson rd.              (314) 993-6699 fax
Suite 475		       mminnis@prefres.com
St. Louis, MO
63141
=========================================================


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Filename globbing/wildcards

[Chris Faylor]

On Wed, Jul 26, 2000 at 03:03:06PM +0100, Derwin, Frank wrote:
>I am doing a simple ls a* in a ksh script.
>
>I've tried it in the bash shell too and I get the same behaviour.

Since the filename expansion for bash and ksh is done in the shells
themselves, it's odd that you would be seeing the same behavior in
both.

A 'cygcheck -r -s -v' might help pinpoint your problem.

cgf

>> -----Original Message-----
>> From:	Chris Faylor [SMTP:cgf@cygnus.com]
>> Sent:	Wednesday, July 26, 2000 2:53 PM
>> To:	'cygwin@sourceware.cygnus.com'
>> Cc:	Frank.Derwin@fid-intl.com
>> Subject:	Re: Filename globbing/wildcards
>> 
>> On Wed, Jul 26, 2000 at 09:48:34AM +0100, Derwin, Frank wrote:
>> >I've just started using the 1.0 Cygwin CD release.
>> >
>> >I have a problem with filename globbing.  A single * expands correctly to
>> >give all filenames.
>> >
>> >But any variation on this (such as a* or *a) gives the error "Filename
>> too
>> >long", whether or not there are files that match the pattern.
>> >
>> >Any suggestions?
>> 
>> I can't duplicate this behavior.  Sorry.
>> 
>> Are you doing this from a command shell?  From bash?  What command are you
>> using?
>> 
>> cgf
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com

-- 
cgf@cygnus.com                        Cygnus Solutions, a Red Hat company
http://sourceware.cygnus.com/         http://www.redhat.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Filename globbing/wildcards

[Earnie Boyd]

--- "Derwin, Frank" <Frank.Derwin@fid-intl.com> wrote:
> Hi,
> 
> I've just started using the 1.0 Cygwin CD release.
> 
> I have a problem with filename globbing.  A single * expands correctly to
> give all filenames.
> 
> But any variation on this (such as a* or *a) gives the error "Filename too
> long", whether or not there are files that match the pattern.
> 
> Any suggestions?
> 

I've a few but I don't know which one fits.  Exactly what is the command you're
using when you see this error?  What shell interpreter are you using?  Paste
the output of `cygcheck -v -r -s' in your response to the list, not to me.

Regards,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Filename globbing/wildcards

[Derwin, Frank]

I am doing a simple ls a* in a ksh script.

I've tried it in the bash shell too and I get the same behaviour.


Regards,

Frank 

> -----Original Message-----
> From:	Chris Faylor [SMTP:cgf@cygnus.com]
> Sent:	Wednesday, July 26, 2000 2:53 PM
> To:	'cygwin@sourceware.cygnus.com'
> Cc:	Frank.Derwin@fid-intl.com
> Subject:	Re: Filename globbing/wildcards
> 
> On Wed, Jul 26, 2000 at 09:48:34AM +0100, Derwin, Frank wrote:
> >I've just started using the 1.0 Cygwin CD release.
> >
> >I have a problem with filename globbing.  A single * expands correctly to
> >give all filenames.
> >
> >But any variation on this (such as a* or *a) gives the error "Filename
> too
> >long", whether or not there are files that match the pattern.
> >
> >Any suggestions?
> 
> I can't duplicate this behavior.  Sorry.
> 
> Are you doing this from a command shell?  From bash?  What command are you
> using?
> 
> cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com