No, it looks like output pane is well hidden. Once it has been shown once, you can get it with undocumented window.get_pane("moo-edit-window-output") call; but the function which creates it for the first time is not exposed to scripts. Why do you need output pane in the first place?
You may be able to do something similar to what you do in code above with a shell script tool: use "Whole document" as input and "Insert into the document" as output. However, I am not sure what happens in case of errors, I am afraid it will just ignore errors: you could work that around by putting the above code into a shell script, and output the document as it is if an error happened. It won't be automatically saved. There is also "Output pane" output kind for shell scripts, if you want it there. All these things are documented in help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1) replace code in edit window if perltidy return no errors
2) show errors (no perltidy errors, errors of "perl -c") if perl syntax is not OK (in output pane, for browse lines with errors)
In "shell script" settings this is impossible(?): or output to pane, or in edit window, depending on the result of the running external script.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can I print text into output pane (from LUA script)?
No, it doesn't look like you can.
Maybe from python? Current thing:
No, it looks like output pane is well hidden. Once it has been shown once, you can get it with undocumented window.get_pane("moo-edit-window-output") call; but the function which creates it for the first time is not exposed to scripts. Why do you need output pane in the first place?
You may be able to do something similar to what you do in code above with a shell script tool: use "Whole document" as input and "Insert into the document" as output. However, I am not sure what happens in case of errors, I am afraid it will just ignore errors: you could work that around by putting the above code into a shell script, and output the document as it is if an error happened. It won't be automatically saved. There is also "Output pane" output kind for shell scripts, if you want it there. All these things are documented in help.
I want:
1) replace code in edit window if perltidy return no errors
2) show errors (no perltidy errors, errors of "perl -c") if perl syntax is not OK (in output pane, for browse lines with errors)
In "shell script" settings this is impossible(?): or output to pane, or in edit window, depending on the result of the running external script.
Right, shell script won't work. It seems you really need internal APIs which aren't exposed currently.
You can try this: http://sourceforge.net/projects/mooedit/files/medit/unstable-1.1.9x/medit-1.1.97-devel.tar.bz2/download
It exposes some functions to scripts, this works in python:
Thanks, it works with lua :)
P.S. In .97 sources i see code folding, and closing icons for individual tabs... not implemented completely?