Log_buddy released - your helpful dev and debug buddy

Ruby
1

LogBuddy is your friendly little log buddy at your side, helping you
dev, debug, and test. It plays well with Rails and plain old Ruby
projects. To use it, sudo gem install log_buddy, then require
‘log_buddy’ and call LogBuddy.init. It will add two methods to object
instance and class level: “d” and “logger”. You probably only want to
use these in non-prod environments, so conditionally load it based on
your test env.

The “logger” method is just a typical logger - it will use the Rails
logger if its available.
The “d” method is a special helper that will output the code in the
block and its result - note that you must use the bracket block form

  • do…end is not supported.

Examples

require ‘lib/log_buddy’
LogBuddy.init
a = “foo”
@a = “my var”
@@bar = “class var!”
def bark
“woof!”
end

module Foo;
def self.module_method
“hi!!”
end
end

d { a } # logs “a = ‘foo’”
d { @a } # logs “@a = ‘my var’”
d { @@bar } # logs “@@bar = ‘class var!’”
d { bark } # logs “bark = woof!”
d { Foo::module_method } # logs Foo::module_method = ‘hi!!’

More

Log bugs/issues/suggestions here:
http://opensource.thinkrelevance.com/wiki/log_buddy
Source: GitHub - relevance/log_buddy: logbuddy is your friendly little log buddy by your side
git clone git://github.com/relevance/log_buddy.git
rdocs: http://thinkrelevance.rubyforge.org/log_buddy/

Thanks

Thanks to Dave T. and his latest testing code for the idea of
simple reading the file based on the call stack to easily output the
log line.
Thanks to Muness Alrubaie for pairing.

  • Rob
2

On Mon, Mar 31, 2008 at 12:47:20PM +0900, Rob S. wrote:

LogBuddy is your friendly little log buddy at your side, helping you
dev, debug, and test. It plays well with Rails and plain old Ruby
projects. To use it, sudo gem install log_buddy, then require
‘log_buddy’ and call LogBuddy.init. It will add two methods to object
instance and class level: “d” and “logger”. You probably only want to
use these in non-prod environments, so conditionally load it based on
your test env.

The growing ubiquity of all administrative commands being explained with
a “sudo” at the front, as if everyone in the world uses sudo for all
administrative commands, is getting kinda old.

  1. Some people use MS Windows.

  2. Some people use MacOS X.

  3. Some people use su or just login as root from the TTY console.

The common thread here is that not everyone in the world is using
Ubuntu.

. . . but LogBuddy looks interesting. I might have to give that a whirl
in the near future. Thanks.

3

Chad P. wrote:

The common thread here is that not everyone in the world is using Ubuntu.

  1. Some people use ubuntu, but chown -R /usr/local to their own user.
    (On my laptop, anyway!) Never have to “sudo gem”.
4

Erm, Mac OS X uses sudo…

–Jeremy

On Mon, Mar 31, 2008 at 12:41 AM, Chad P. [email protected]
wrote:

a “sudo” at the front, as if everyone in the world uses sudo for all
. . . but LogBuddy looks interesting. I might have to give that a whirl
in the near future. Thanks.

–
CCD CopyWrite Chad P. [ http://ccd.apotheon.org ]
Thomas McCauley: “The measure of a man’s real character is what he would do
if he knew he would never be found out.”

–
http://jeremymcanally.com/
http://entp.com

Read my books:
Ruby in Practice (Ruby in Practice)
My free Ruby e-book (http://humblelittlerubybook.com/)

Or, my blogs:

http://rubyinpractice.com