I said: > Tuomo suggested one way of doing this (using bdoc), another might be to use a > menu structure to represent commonly used commands and set up a > helper-function that would call a particular menu entry, which would then be > bound rather than the lua code itself.
Actually, a better solution would probably be to simply create a table consisting of command names and strings of lua code implementing them. The helper function would simply evaluate to the lua string, which would get bound. No real need to get it messed up with the menu structures. If desired there could be a lookup table of documentation for the commands as well. The slightly tricky bit would be to account for the different sorts of options passed in the binding (_, _sub, etc.). Simplest would be to make different ways of calling the lua function different commands, where necessary. -- Jeremy Hankins <[EMAIL PROTECTED]> PGP fingerprint: 748F 4D16 538E 75D6 8333 9E10 D212 B5ED 37D0 0A03
