On Mon, Mar 03, 2008 at 11:03:24AM -0500, Mark J. Reed wrote: > On Mon, Mar 3, 2008 at 10:44 AM, Richard Cobbe <[EMAIL PROTECTED]> wrote: > > On Mon, Mar 03, 2008 at 09:47:41AM -0500, Mark J. Reed wrote: > > > If it's using sed to build a regex and match against that, is it > > > quoting regex metachars? If not you could replace the spaces with > > > periods and it should work - although it would also prune any other > > > paths that were the same other than replacing the space with > > > something else. > > > > Ah, a good thought. No, it isn't checking for regexp metachars. > > If it's using /sw/bin/sed (GNU verison), then you could use string > escapes to specify the spaces, e.g. \d32 or \o40 or \x20. But those > are a GNU extension not supported by the sed that ships with OS X in > /usr/bin.
It merely calls sed without specifying a path, so it depends on which is first in the PATH that cron gives it. It's safest to assume OS X's sed, I think. > > In any case, I'll submit a bug/feature request about this to the upstream > > folks soon. > > Bug. Not being able to specify pathnames with spaces is a defect, not > a missing feature. I know that and you know that, but in the past I've run into Unix folks whose reaction to this kind of problem is to say "don't use spaces in pathnames then." This doesn't appear to be irony, either. Bug submitted: <https://savannah.gnu.org/bugs/index.php?22467>. We'll see what happens. Richard ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
