unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Some error info from configure.bat please
Date: Sun, 03 Jul 2005 20:58:17 +0200	[thread overview]
Message-ID: <umzp3pvhy.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b0507030927582cc1b8@mail.gmail.com> (message from Juanma Barranquero on Sun, 3 Jul 2005 18:27:05 +0200)

> Date: Sun, 3 Jul 2005 18:27:05 +0200
> From: Juanma Barranquero <lekktu@gmail.com>
> Cc: emacs-devel@gnu.org
> 
> On 7/3/05, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> >  (the "**" feature alone is something to kill for)
> 
> Could you please describe it briefly?

"fgrep STRING /foo/bar/**/*.c" will look for the named string in all
*.c files in /foo/bar and in all its subdirectories, recursively (and
is much faster than "fgrep -R STRING /foo/bar/**/* --include='*.c'"
you will need without the ** feature).

Likewise, "ls -ltrd d:/**/*.log" will produce a listing of all the
*.log files on drive D:, in the order they were created/modified.

Convinced?

  reply	other threads:[~2005-07-03 18:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-02  9:32 Some error info from configure.bat please Lennart Borgman
2005-07-02 13:22 ` Eli Zaretskii
2005-07-02 12:32   ` Lennart Borgman
2005-07-02 16:53     ` Eli Zaretskii
2005-07-02 16:01       ` Lennart Borgman
2005-07-02 16:34         ` Juanma Barranquero
2005-07-02 17:36         ` Eli Zaretskii
2005-07-02 20:24           ` Jason Rumney
2005-07-02 21:16             ` Juanma Barranquero
2005-07-02 21:37               ` Jason Rumney
2005-07-02 21:45                 ` Lennart Borgman
2005-07-02 22:20                   ` Jason Rumney
2005-07-03  6:19                     ` Eli Zaretskii
2005-07-02 21:37               ` Lennart Borgman
2005-07-03  0:22                 ` Juanma Barranquero
2005-07-03  0:54                   ` Lennart Borgman
2005-07-03  1:14                     ` David Kastrup
2005-07-03  1:40                       ` Juanma Barranquero
2005-07-03  8:19                         ` David Kastrup
2005-07-03 10:42                           ` Juanma Barranquero
2005-07-03  1:21                     ` Juanma Barranquero
2005-07-03  6:30                     ` Eli Zaretskii
2005-07-03  7:29                       ` Lennart Borgman
2005-07-03 16:02                         ` Eli Zaretskii
2005-07-03  7:50                       ` Lennart Borgman
2005-07-03 16:11                         ` Eli Zaretskii
2005-07-03 16:27                           ` Juanma Barranquero
2005-07-03 18:58                             ` Eli Zaretskii [this message]
2005-07-03 18:17                               ` Juanma Barranquero
2005-07-04 14:54                               ` Stefan Monnier
2005-07-04 15:17                                 ` Andreas Schwab
2005-07-04 18:07                                   ` Stefan Monnier
2005-07-04 18:45                                     ` Lennart Borgman
2005-07-16 12:39           ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=umzp3pvhy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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