On 19 June 2006 12:45, ydubost wrote:
> Hello there,
>
> I have been working on a very simple script for 3 hours not been able to
> understand what's wrong with it.
Run it under "bash -x" to see what's actually being executed and so what's
going wrong.
> TYPE_FIC_UPPER="._BC ._CH ._CL ._CM ._DF ._DL ._EV ._FL ._GR ._HL ._IS ._MB
> ._MM ._MP ._OV ._PR ._SN ._SY ._TI ._TR"
> TYPE_FIC_LOWER="._bc ._ch ._cl ._cm ._df ._dl ._ev ._fl ._gr ._hl ._is ._mb
> ._mm ._mp ._ov ._pr ._sn ._sy ._ti ._tr"
> TYPELIST=${TYPE_FIC_UPPER}" "${TYPE_FIC_LOWER}
>
> Extension=$(echo ${TYPELIST} | sed -e's:[ ][.]:" -o -name "*.:g' | sed
> -e's:^[.]:-name ":' | sed -e's:$:":')
> MaCommande="find . ${Extension} -exec rm {} \; -print"
>
> echo -e " - lancement de la commande=\n[${MaCommande}]\n" # display OK !
>
> $(${MaCommande}) # ne fonctionne pas !
^^^^^^^^^^^^^^^
Don't you just want "${MaCommande}" on it's own? Or "$(echo ${MaCommande})"
perhaps?
> find . ${Extension} -exec rm {} \; -print # ne fonctionne pas non plus !
Do any of the filenames or subdirectories have spaces or other special
characters?
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
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/
