public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hannu E K Nevalainen" <garbage_collector@telia.com>
To: <cygwin@cygwin.com>
Subject: RE: Wildcard problem with recursion
Date: Sat, 25 Oct 2003 16:54:00 -0000	[thread overview]
Message-ID: <NGBBLLIAMFLGJEOAJCCEMEMGDFAA.garbage_collector@telia.com> (raw)
In-Reply-To: <000001c39abd$12b7fcd0$9c01a8c0@shakti.tallysolutions.com>

> From: Ajith Kumar
> Sent: Saturday, October 25, 2003 7:59 AM

> > Yes, read the shell man pages to learn how file completion works.
> > What you want is a job for `find | xargs grep'.
> >
> > Corinna

> I run these from the win2k cmd.exe and not from the bash prompt.
> Can u be more specific please to which doc or man pages I shold
> refer to?
> Thank You
> Regards,
> ajith

$ info bash # bash shell info pages (hypertext)
 (some man pages are updated less requently than info pages)
$ info find
$ info xargs

In most cases you can replace "info" with "man" - but note that man pages
often are less frequently updated.

If
	$ type -a <command>
says "Internal command" then
	$ help <command>
usually tells more.

Though you might find it easier to find relevant parts of the text by using
less's "/" key to search for interesting text in the _man_ pages  (this
works in the info pages too, but is less succesful IMO)

/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/

      reply	other threads:[~2003-10-25 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-23 10:05 Ajith Kumar
2003-10-23 12:54 ` Corinna Vinschen
2003-10-24 10:47   ` Andy Rushton
2003-10-25 10:17     ` Ajith Kumar
2003-10-25 10:03   ` Ajith Kumar
2003-10-25 16:54     ` Hannu E K Nevalainen [this message]

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=NGBBLLIAMFLGJEOAJCCEMEMGDFAA.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).