00:54 <UberDragon> is there anyway to set the output to shell level? I don't want to log to a file.. but I want to control what is displayed on screen while bot runs

01:10 <catepillar> UberDragon: it should default to stdout

01:11 <UberDragon> right now I have in my bot.rb -> http://pastebin.com/aKkLXsYX

01:11 <UberDragon> the third line seems to control what goes to stdout

01:12 <UberDragon> but it doesn't work without the first line (which logs everything to file)

01:18 <UberDragon> and without those lines.. stdout is full on debug mode heh

01:26 <UberDragon> for now I'm just auto deleting the file everytime the bot is initialized but still would rather figure out the "right way" to handle it

02:29 <catepillar> sorry, got a bit distracted... you are trying to send some things to a log file, and print others on stdout?

02:35 <catepillar> a hacky way to do it if you are using linux is to open "/dev/null" for your file

02:43 <catepillar> and just using bot.loggers = :warn is working for me

02:51 <UberDragon> if I use just bot.loggers = :warn it hangs before connection :/

02:52 <catepillar> it's not printing anything out

02:52 <catepillar> but it's still connecting for me

02:52 <catepillar> and i wouldn't expect it to be printing with a level of warn

02:53 <UberDragon> hm

02:53 <UberDragon> I set mine to :log

02:53 <UberDragon> to be perfectly honest

02:54 <UberDragon> same result if I set to :debug

02:54 <catepillar> is yours failing to connect with :log?

02:55 <UberDragon> yes, the message about trying to connect to server never shows up and it just hangs

02:55 <UberDragon> last thing I see is webrick starting up

02:56 <catepillar> and you are giving it a valid server to connect to?

02:56 <UberDragon> yes.. if I remove the bot.logger line it connects in debug stdout

02:56 <UberDragon> if I add the three lines from my pastebin link it connects as expected

02:57 <UberDragon> it never gets to the bot.start lines (bot.logger is just above it)

02:58 <catepillar> that's how I have been testing

02:58 <catepillar> i have the config block just above it

02:59 <catepillar> then a single bot.loggers = :warn # or :log or :debug

02:59 <catepillar> then bot.start

02:59 <UberDragon> yup same here.. config block above.. then logger line.. then bot start thread block

02:59 <catepillar> everything is working how I would expect it to

03:00 <catepillar> might need someone more experienced than me to weigh in here

03:03 <UberDragon> /dev/null works :P

03:04 <UberDragon> bot loads right up.. and at least I don't have to clean up log files

03:04 <UberDragon> hehe

03:29 <UberDragon> looks like I can ommit the 1st line.. and use the 2nd and third.. all works as expected and no /dev/null log ;)

03:34 <UberDragon> !plugin reload ChannelStats

03:34 <UberDragon> mt