unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mike Mattie <codermattie@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: traverse a directory
Date: Fri, 4 Jan 2008 16:46:58 -0800	[thread overview]
Message-ID: <20080104164658.6c19fcbe@reforged> (raw)
In-Reply-To: <873atgvxm7.fsf@W0053328.mgh.harvard.edu>


[-- Attachment #1.1: Type: text/plain, Size: 1179 bytes --]

On Wed, 02 Jan 2008 14:25:04 -0500
jadamson@partners.org (Joel J. Adamson) wrote:

> Mike Mattie <codermattie@gmail.com> writes:
> 
> > On Wed, 02 Jan 2008 13:03:39 -0500
> > jadamson@partners.org (Joel J. Adamson) wrote:
> >
> >> Mike Mattie <codermattie@gmail.com> writes:
> >> 
> >> > On Tue, 1 Jan 2008 08:51:33 -0800 (PST)
> >> > Xah Lee <xah@xahlee.org> wrote:
> >> >
> >> >> if i want to recurse into a directory, do i have to write my
> >> >> own?
> >> 
> >> I know that doing this in Emacs is especially cool, but "find ...
> >> exec {}\;" should do the trick.
> >> 
> >> Joel
> >> 
> >
> > cool maybe, but portable was my reason for doing it this way. BSD
> > find is very different from gnu find.
> 
> So I've heard: should I go ahead with installing FreeBSD?

I sure don't know. Whatever you like the best. I just post
code if I think it's apropos. Sometimes it is, and when
it isn't someone usually mentions where the canonical
implementation is located within the Emacs distribution.
 
> > some systems don't even have find. exec is a jungle, posix a
> > mirage :)
> 
> Some systems I've found aren't systematic.
> 
> Joel
> 

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 152 bytes --]

_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

  parent reply	other threads:[~2008-01-05  0:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-01 16:51 traverse a directory Xah Lee
2008-01-01 20:22 ` Eli Zaretskii
2008-01-02  5:43 ` Mike Mattie
     [not found] ` <mailman.5612.1199252679.18990.help-gnu-emacs@gnu.org>
2008-01-02 18:03   ` Joel J. Adamson
2008-01-02 19:04     ` Mike Mattie
     [not found]     ` <mailman.5637.1199300789.18990.help-gnu-emacs@gnu.org>
2008-01-02 19:25       ` Joel J. Adamson
2008-01-03  5:51         ` Xah Lee
2008-01-03 11:16           ` Alexey Pustyntsev
2008-01-03 16:25           ` Joel J. Adamson
     [not found]           ` <bf802645-6c07-46d6-b968-1067c1ff4c7f@d21g2000prf.googlegro ups.com>
2008-01-05 17:47             ` OT: " Johan Lindström
2008-01-05  0:46         ` Mike Mattie [this message]
     [not found] ` <mailman.5595.1199218943.18990.help-gnu-emacs@gnu.org>
2008-01-03  4:30   ` Xah Lee

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=20080104164658.6c19fcbe@reforged \
    --to=codermattie@gmail.com \
    --cc=help-gnu-emacs@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.
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).