annotate print_log.lua @ 149:df0ca8ed1aff

Be smarter when joining a raid. Add some more flow-control debug printing. Given (A) joining a raid, which triggers a delayed addon load, and seeing the "what to do next" popup, and (B) restoring previous data which contains only a raid roster or generated text, fix the interaction in which the activation from (B) overrides the user's choice in (A)'s popup.
author Farmbuyer of US-Kilrogg <farmbuyer@gmail.com>
date Thu, 08 Jan 2015 15:22:27 -0500
parents 8f7ec6ccf5e3
children
rev   line source
farmbuyer@19 1 #!/usr/bin/env lua
farmbuyer@19 2
farmbuyer@39 3 --[[
farmbuyer@39 4 This is meant to be run from a command-line interpreter. It's what I
farmbuyer@39 5 use in practice, but is shipping primarily an example.
farmbuyer@39 6 ]]
farmbuyer@39 7
farmbuyer@19 8 if not arg[1] or arg[1] == "" then
farmbuyer@19 9 print"Usage: lua print_log.lua /path/to/OuroLoot_savedvars.lua"
farmbuyer@19 10 print"Don't forget to delete log table after viewing!"
farmbuyer@19 11 os.exit(1)
farmbuyer@19 12 end
farmbuyer@19 13
farmbuyer@19 14 dofile(arg[1])
farmbuyer@19 15
farmbuyer@19 16 if type(OuroLootSV_log) ~= 'table' then
farmbuyer@19 17 print("Did not find OuroLootSV_log in", arg[1])
farmbuyer@19 18 os.exit(1)
farmbuyer@19 19 end
farmbuyer@19 20
farmbuyer@19 21 for _,v in ipairs(OuroLootSV_log) do
farmbuyer@19 22 print(v)
farmbuyer@19 23 end
farmbuyer@19 24
farmbuyer@19 25 os.exit(0)
farmbuyer@19 26
farmbuyer@19 27 -- vim:noet ff=unix