Minor fixes: README markup and tutorial line number
This commit is contained in:
parent
a37cc46213
commit
bac047454b
|
@ -81,7 +81,7 @@ There are several overloadable functions you can use to customize debugger.lua.
|
|||
* `dbg.write(str)` - Write a string to the output. (Defaults to write to stdout)
|
||||
* `dbg.shorten_path(path)` - Return a shortened version of a path. (Defaults to simply return `path`)
|
||||
* `dbg.exit(err)` - Stop debugging. (Defaults to `os.exit(err)`)
|
||||
* `dbg.pretty(obj)' - Output a pretty print string for an object. (Defaults to a reasonable version using __tostring metamethods and such)
|
||||
* `dbg.pretty(obj)` - Output a pretty print string for an object. (Defaults to a reasonable version using __tostring metamethods and such)
|
||||
|
||||
Using these you can customize the debugger to work in your environment. For instance, you can divert the I/O over a network socket or to a GUI window.
|
||||
|
||||
|
|
|
@ -21,7 +21,7 @@ print[[
|
|||
as well as which function you are in.
|
||||
Keep a close watch on this as you follow along.
|
||||
It should be stopped a line after the dbg() call.
|
||||
(Line 86 unless I forgot to double update it)
|
||||
(Line 88 unless I forgot to double update it)
|
||||
|
||||
Sometimes functions don't have global names.
|
||||
It might print the name of a method, local variable
|
||||
|
|
Loading…
Reference in New Issue