http://forums.worldofwarcraft.com/thread.aspx?Foru...
BigMacro v1.03 by Jooky
Have you run out of macro slots? Are you tired of the 256-character limit on macros? Do you wish you could bind a key to a macro without wasting an action-bar slot? Then BigMacro is for you!

BigMacro gives you 30 keybindable macros, unlimited in length. (Many thanks to Mook/Talissanti for increasing the number of macros from 10 to 30).

Installation:
-------------
Extract the contents of the .zip archive into your .\World of Warcraft\Interface\Addons folder.

Usage:
----------
Use any text editor to edit the .\World of Warcraft\Interface\Addons\BigMacro\Macros.lua file.
Create your new'extended' macro in one of the macro##={ } blocks.
Each line of the macro should be surrounded by [[ and ]].

An example section of this would be something like:
macro01={
[[/party Incoming heal to %t]],
[[/script BM_CastSpellByName("Holy Light","Rank 1")]],
},

Launch WoW and bind your macro to a key using your in-game keybinding menu.

You can also attach your extended macro to an in-game macro. To do so, Launch WoW and type"/macro" to bring up the in-game macro interface. Create a new macro that calls your new'Big Macro'.
You can call your new'Big Macro' using the following commands:
"/bm X"
or
/script BigMacro_Execute("macroYY")
X is the macro number between (1 and 30) and YY is the two-digit macro number between (01 and 30) that matches the one in the Addons\BigMacro\Macros.lua file.

To turn echoing of macros on and off, use:
/bm echo on
/bm echo off


Tips:
----------
Due to Blizzard's anti-botting policies, if you attempt to run your BigMacro directly from a'chat line' (ie. not bound to a button) calls to cast spells may not fire. Make sure you activate your macros with a button-press or mouse-click.

To reliably cast spells, use /script BM_CastSpellByName("Spell Name","Rank #")
Example: /script BM_CastSpellByName("Frost Armor","Rank 1")
If no rank is given, then the highest ranking spell of that name will be used.

Both"/cast" and"/script CastSpellByName" should work under normal usage, but may not work properly in certain situations. The above method is much more reliable.