[Enhancement] Separate outputs with an empty line

[Yaron10]

vs.

Thank you.

[sasumner]

I see the empty lines in the top image, but the bottom image doesn't really relate to the content of the top image so I am confused about what is really wanted here?

[Yaron10]

Simply add an empty line after each output segment.

At the top image it's instantly clear there are three different segments.
Looking at the bottom image you see "one block".

Setting the command's foreground color to blue would make the output even clearer IMO.
That is:

Command [in blue]
Result [in black]

[sasumner]

The top image seems to be initialization? Once initialization is over, then things that happen in the console look like the bottom image, so there's no extra spacing needed? If code writes to the console it could/should put its own spacing in when it is done. Otherwise, is this feature supposed to "watch" code and if it writes anything at all to the console, this feature should add an empty line when the code has finished (and if the code hasn't written anything then no empty line should be added?).

[Yaron10]

Currently a single \n is inserted after each output.
My suggestion is to insert \n\n for a better clarity.

To be honest, I think this is something for userdefined startup.py files
Something like

class ModifiedConsoleOut:
    def __init__(self):
        global console
        self._console = console;

    def write(self, text):
        self._console.write(text+'\n');

sys.stdout = ModifiedConsoleOut()

or if you want to have more control over the spacing you can use something like this

console.editor.setExtraAscent(2)
console.editor.setExtraDescent(2)

[Yaron10]

@ClaudiaFrank,

I'd like to make sure we understand each other correctly.

If you run editor.getCurLine() 5 times, this is the output:

>>> editor.getCurLine()
'// Note that the GPL places important restrictions on "derived works", yet\r\n'
>>> editor.getCurLine()
'// Note that the GPL places important restrictions on "derived works", yet\r\n'
>>> editor.getCurLine()
'// Note that the GPL places important restrictions on "derived works", yet\r\n'
>>> editor.getCurLine()
'// Note that the GPL places important restrictions on "derived works", yet\r\n'
>>> editor.getCurLine()
'// Note that the GPL places important restrictions on "derived works", yet\r\n'

Wouldn't it be much clearer like this?

>>> editor.getCurLine()
'// Note that the GPL places important restrictions on "derived works", yet\r\n'

>>> editor.getCurLine()
'// Note that the GPL places important restrictions on "derived works", yet\r\n'

>>> editor.getCurLine()
'// Note that the GPL places important restrictions on "derived works", yet\r\n'

>>> editor.getCurLine()
'// Note that the GPL places important restrictions on "derived works", yet\r\n'

>>> editor.getCurLine()
'// Note that the GPL places important restrictions on "derived works", yet\r\n'

---

class ModifiedConsoleOut:
    def __init__(self):
        global console
        self._console = console;

    def write(self, text):
        self._console.write(text+'\n');

sys.stdout = ModifiedConsoleOut()

Does not achieve that.

console.editor.setExtraAscent(2)
console.editor.setExtraDescent(2)

Increases the spacing between all lines but does not separate the different segments.

Thank you.

So you are looking for solution just for the output generated by commands execute via the "run area", correct?

[Yaron10]

Indeed.

[Yaron10]

Allow me a correction.

I was initially thinking about outputs generated after using the console input.
But actually any console output not initiated directly by the user - PS should make sure to insert an empty line and separate its messages.

That is:
If console.write() is used in a script, the user can add as many \n as they want.
However, error messages generated by PS (e.g. wrong syntax in a script) should be separated by an empty line.

It's not that important for my personal use.
If you don't think it's a worthy enhancement, please let me know and I'll close the issue.

Thank you.

Actually I like your approach, unfortunately it looks like it isn't that easy to implement reasonably well.
Currently I only found the way to add

textToWrite.append((textToWrite != "\n") ? "\n" : "");

to void PythonConsole::writeText(boost::python::object text) before GILRelease and only for normal output.
Error output is sent in multiple text so that nearly each line does get an additional extra EOL.

[Yaron10]

Thank you Claudia.

Should I close the issue or you'd like to keep trying?

Please keep it open - I don't throw it in the towel yet.

[Yaron10]

👍
Go for it! :)

Thanks.

[sasumner]

I suppose the one thing I don't care for about this is I would have to devote more screen real estate to my PS console window to see the same amount of information. I like keeping my editor tab area as large as possible for obvious reasons, so while I like having other things (consoles, find results, clipboard history panel, etc) viewable, they are secondary and I like them to be as compact as possible. My 2c.

[Yaron10]

@sasumner,

I see your point.
I suppose a user-preference can set this behavior.

---

What do you think about the following suggestion?

Setting the command's foreground color to blue would make the output even clearer IMO.
That is:

Command [in blue]
Result [in black]