yes - usually that was the prompt for the terminal to insert a new line ... on
some terminals this is a behaviour you can't control as it's implemented in
hardware, so curses fakes things by moving the cursor back to where it "should"
be afterward.
If you try and to something when the cursor is
On Wed, Feb 27, 2019 at 8:09 PM Alex Kleider wrote:
>
> On 2019-02-27 17:48, boB Stepp wrote:
> > Under https://docs.python.org/3/library/curses.html#window-objects in
> > the curses docs, it states:
> >
> >
> > window.addch(ch[, attr])
> > window.addch(y, x, ch[, attr])
> > [...]
> >
> > Note
>
On 2019-02-27 17:48, boB Stepp wrote:
Under https://docs.python.org/3/library/curses.html#window-objects in
the curses docs, it states:
window.addch(ch[, attr])
window.addch(y, x, ch[, attr])
[...]
Note
Writing outside the window, subwindow, or pad raises a curses.error.
Attempting to write t
Under https://docs.python.org/3/library/curses.html#window-objects in
the curses docs, it states:
window.addch(ch[, attr])
window.addch(y, x, ch[, attr])
[...]
Note
Writing outside the window, subwindow, or pad raises a curses.error.
Attempting to write to the lower right corner of a window, su
