Help using WriteLog() function about micro HOT 7 CLOSED

I don't have time just right now to answer but you can use micro.Log(err). It will output to log.txt file although you will need to run micro with micro -debug

from micro.

What error message do you get when it crash?

from micro.

Hi

Many thanks for your reply.

• I want to use the LogBuf in the same way the plugin available command displays output.

• I think the Log.txt is a different beast, for debugging the application.

• I don't get an error message the console dies and disappears (It may be because I am running a batch file to launch Micro).

Kind Regards Gavin Holt

from micro.

I think the Log.txt is a different beast, for debugging the application.

Yeah

I don't get an error message the console dies and disappears (It may be because I am running a batch file to launch Micro).

Maybe try to open not with batch file? It usually say when error in plugin and what is an error. Idk if it will help but know what it prints wouldn't be bad

want to use the LogBuf in the same way the plugin available command displays output.

Ok. What I found:

When you print > plugin available internally micro opens logbuffer (which is io.Writer) and sends it to another function

that prints to buffer via fmt.Fprintln(out, <text>)

P.S it won't help with WriteLog but you can write there as you wanted.

from micro.

-- How to detect if its already open ?
Current:OpenLogBuf()

I think no way to do it as we expected in just one line

> log don't check if log buffer is open it just checks if you ran it from log buffer.

1. > log
2. Ctrl+w to switch to non logbuf
3. > log

You will see two bufpanes with the same content. But if you run > log from log buf, it will just close it. If you want to check if log buf is currently opened you will need to iterate thorough all the panes and check if one of them is log buf. Idk I will try to do more research

from micro.

It looks like a sorta bug. We have only one pointer for global LogBufPane so we must have only one log pane at the moment. But in previous comment I said how to do it. Am I right it is a bug? @dmaluka @JoeKar

Does comment rely on the fact it is opened only by ToggleLogCmd?

It is easy to correct for > log dustdfg@da2d4cf but I am not sure what to do with

And I still don't know what causes problem of issues OP

from micro.

Hi

I have been silly. Reading the Plugins.md I found the bufffer.Log function!

So to write to the global LogBuf is literally:

buffer.Log("Hello World").

However, be sure to use tostring() beforehand as there is no built in type conversion:

buffer.Log(8) -- Fails

Kind Regards Gavin Holt

I will leave the problem of multiple Log splits for brighter minds.

from micro.