On Tue, Jan 14, 2020 at 10:13 AM Alexander Gabriel <[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.
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.
--
> 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/2a1ae7e6-aa39-4b6e-b77f-18e86ea9884f%40googlegroups.com
> <https://groups.google.com/d/msgid/opencog/2a1ae7e6-aa39-4b6e-b77f-18e86ea9884f%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
cassette tapes - analog TV - film cameras - you
--
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/CAHrUA353tQ4G91-XDRevCJpuK1KTd5mW16tHypT-0BYSb_2N_g%40mail.gmail.com.
