Quentin Peter

I guess the problem here is what the expected behaviour is. There is mainly two possible behaviour: - The console scrolls down no matter what on new output. So if...

Probably related to https://github.com/jupyter/qtconsole/issues/386 There is a bug with autoscroll and remote commands.

This is what I have with the current master (which should be similar to 4.5.5) on MacOS Catalina 10.15:  Could you send a video of what you have?

If you found a bug you can look at #360 for inspiration :)

In `qtconsole/console_widget.py`, the scrolling for `_insert_plain_text` works as follow: (Maybe this should be generalised for any input) - Check if the end is visible before adding the text (`end_doc_pos -...

@bakeryproducts You don't want to scroll down if the user is looking at something above, otherwise you can't read anything if the console is constantly scrolling down. The console should...

> > I get a lot of No such comm warnings > > Maybe this problem is caused by the introduction of comms to qtconsole. Please downgrade to qtconsole 4.4.4...

PR spyder-ide/spyder#1478 solves that problem, but only for consoles started from spyder. Also, if another client connects to the same console, it wouldn't recieve the messages either. The ipython kernel...

I haven't investigated this particular issue, but in general, handling `KeyboardInterrupt`is the user code responsability, so there is little we can do. For example the following code can not be...

> However, if there is different behavior between inside Spyder and in QtConsole, or at least `ipython`, then that perhaps should be investigated. I completely agree