Re: Give parts of commands/definitions to a called command (to parse arguments)

On Fri, Apr 22, 2016 at 01:49:48 +0200, Oliver Bandel wrote:

> Zitat von Oliver Bandel <[email protected]> (Fri, 22 Apr 2016
> 01:37:28 +0200)
> 
> >Zitat von Valery Ushakov <[email protected]> (Thu, 21 Apr 2016 00:10:15
> >+0300)
> >
> >>On Wed, Apr 20, 2016 at 19:33:38 +0200, Oliver Bandel wrote:
> >>
> >>>def vvec
> >>> right body
> >>> { pmatrix strut { Yes }  body }
> >>>
> >>>The body is nor parsed again, so it is not seen as command, when using
> >>>
> >>>   vvec { row col a row col b row col c }
> >>>
> >>>inside @Eq.
> >>[...]
> >>>Or are there other ways to achieve my goal?
> >>
> >>Just use a macro.  "pmatrix" itself is a macro that supplies some
> >>additional paramters to "matrix".
> >>
> >>   import @Math macro vvec { pmatrix strut { Yes } }
> >[...]
> >
> >Thanks, that works :-)
> 
> But... the macro - as far as  I can see - creates
> different output than the original command.
> The vector is set slightly more slim with the macro.
> So, somehow the spacing seems to be different...
> Any ideas on that?

Look identical to me at 300% zoom.


> But it throws a message:
> 
> "no value for context variable `EqCurrStyle', using the empty string"
> 
> What's this about?
> Can it become a problem, which yields to dropped objects?

I'm sorry but a wood nymph has stolen my amulet of ESP :).  Can't tell
anything about code I don't see.


-uwe