Message-ID: <45A64B75.B6ABC9F0@dessent.net>
Date: Thu, 11 Jan 2007 06:36:37 -0800
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: cygwin-email utility clipping attached zips
References: <006701c734d6$d8531e00$a501a8c0@CAM.ARTIMI.COM> 	 <45A520B8.7090802@wi.rr.com> <45A52736.2040009@gmx.de> 	 <45A5292A.20606@gmx.de> <45A52E6C.61D53739@dessent.net> <17393e3e0701101200m630f651ch5fe9b623fe7d33b@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Matt Wozniski wrote:

> > email user@example -s test -a "$(sh -c 'IFS=,; echo "$*"' -- *.pdf)" \
> >                 <sample.txt
> 
> But that won't work for files with commas in the name!  (Rare, but it
> can happen...)  I'd prefer something like

This still works fine for filenames with commas since it uses $* which
joins the positional parameters which have already been split (before
the subprocess was even invoked), before IFS is changed to ",".

But if a filename has a comma in its name then it is impossible to
express it as a list of comma-separated filenames without some form of
quoting.  And I doubt that the email program has backslash-escape
parsing logic for this very rare case (but I haven't checked.) 
Regardless, this:

> email user@example -s test -a "$(ls -1 *.pdf | tr '\n' ',' )" < sample.txt

...does not solve the problem either.  You get the same output as above,
except with an erronious trailing ",".

Brian

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