On 1/14/20 6:56 PM, Linas Vepstas wrote:
On Tue, Jan 14, 2020 at 10:13 AM Alexander Gabriel <[email protected]
<mailto:[email protected]>> wrote:
and if I set the cog-logger also to debug I find ure and cog debug
messages.
I wasn't aware there were different loggers.
I'm not sure how they designed the logger code, I think its supposed to
just be a flag for tracing a sub-component.
No, they are different loggers, however they are allowed to point to the
same destination. But they can be configured independently, which is
convenient when you want to log different components with different levels.
BTW, in guile, you can get documentation by typing ,d or ,describe for
example:
scheme@(guile-user)> ,describe cog-logger-set-stdout!
cog-logger-set-stdout! [LOGGER] BOOL
If BOOL is #t, send log messages to stdout; else don't.
If LOGGER is not provided then use the default logger
Returns the previous setting.
Unfortunately, not everything has documentation:
scheme@(guile-user)> ,describe ure-logger-set-stdout!
#f
What I still don't see are any messages from the actual backward
chaining process..
Don't know. Nil knows all.
Nil is an abstraction, and like any abstraction, he loses information
(and didn't write docstrings for these helpers).
Nil
--
You received this message because you are subscribed to the Google Groups
"opencog" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/opencog/382d9f16-c5d9-3a9b-b217-e19c54cb5edc%40gmail.com.
