dani
January 21, 2010, 3:15am
1
I have a macro:
macro -p / mymacro run myscript $pargs
in myscript I have:
echo 1-$arg1 2-$arg2 3-$arg3
if I type:
output will be:
I think pargs should somehow preserve the integrity of parameters so that in the example above arg2 would be “two and two”
I find that when calling scripts which take a long string as a parameter (ie. “this is the comment I need to pass as a single parm”) I have to jump through a few hoops - if I can make it - to get around this bug.
tx
dani
January 30, 2010, 2:25am
2
bump - This is happening too many times in too many scripts (which need pargs in the macros that call them because of too many args can be passed)…
it’s driving me nuts to get around it! and I think it’s a bug that shouldn’t take long to fix (or maybe I’m wrong).
d
rob
February 4, 2010, 6:11pm
3
dani:
bump - This is happening too many times in too many scripts (which need pargs in the macros that call them because of too many args can be passed)…
it’s driving me nuts to get around it! and I think it’s a bug that shouldn’t take long to fix (or maybe I’m wrong).
d
We now have a solution we’re currently evaluating to see if it interfers with other existing scripting methods.
dani
February 4, 2010, 8:03pm
4
that would be great - I was just being frustrated about it this morning too…
rob
February 8, 2010, 8:25pm
5
Ive just committed a fix for the next experimental. Hopefully this doesn’t introduce
Cheers
EDIT: found some unexpected parsing artifacts… Holding off on this change a bit longer…
tx d