You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two small gripes with the Python editor in digabi. As they are relatively different, I've decided to split them into two separate issues. The other can be found here: #692. I might take a crack at implementing these myself over the coming days and I'll make a single pull request for them both if I manage to succeed.
The issue
When using stdin, the input is omitted from the program's output.
As the output of a program is often screenshotted as the answer to exam questions, it would make it clearer to any 3rd parties what the program is actually doing if the stdin would be visible on output.
This change also better mimics the behaviour of most terminals. For example, PowerShell behaves like this:
Solution
After the user has provided the input()/stdin with a value, the prompt + user given input are written onto output similar to PowerShell for example. In a perfect world I could use Solution 2 from #692 and merge everything into a single output buffer similar to most terminals, but its implementation still has some question marks around it. If it is decided that the best way is to proceed with Solution 2, it could be discussed whether stdin should be coloured cyan as stderr is planned to be coloured red in Solution 2, but I haven't made any concrete plans with a cyan stdin yet. If it is decided that the plan forward with the aforementioned issue is Solution 1, then I see no point in colouring the stdin as it makes the scope of this feature's implementation too big and also makes the program's output quite messy.
The text was updated successfully, but these errors were encountered:
I have two small gripes with the Python editor in digabi. As they are relatively different, I've decided to split them into two separate issues. The other can be found here: #692. I might take a crack at implementing these myself over the coming days and I'll make a single pull request for them both if I manage to succeed.
The issue
When using stdin, the input is omitted from the program's output.
As the output of a program is often screenshotted as the answer to exam questions, it would make it clearer to any 3rd parties what the program is actually doing if the stdin would be visible on output.
This change also better mimics the behaviour of most terminals. For example, PowerShell behaves like this:
Solution
After the user has provided the input()/stdin with a value, the prompt + user given input are written onto output similar to PowerShell for example. In a perfect world I could use Solution 2 from #692 and merge everything into a single output buffer similar to most terminals, but its implementation still has some question marks around it. If it is decided that the best way is to proceed with Solution 2, it could be discussed whether stdin should be coloured cyan as stderr is planned to be coloured red in Solution 2, but I haven't made any concrete plans with a cyan stdin yet. If it is decided that the plan forward with the aforementioned issue is Solution 1, then I see no point in colouring the stdin as it makes the scope of this feature's implementation too big and also makes the program's output quite messy.
The text was updated successfully, but these errors were encountered: