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
cocalc now properly works; also add a concrete example of an "astral plane unicode" identifier, so anybody can easily see what happens in the Jupyter client of their choice.
Copy file name to clipboardExpand all lines: docs/messaging.rst
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1457,17 +1457,18 @@ Frontends claiming to implement protocol 5.2 **MUST** identify cursor_pos as the
1457
1457
Kernels may choose to expect the UTF-16 offset from requests implementing protocol 5.1 and earlier, in order to behave correctly with the most popular frontends.
1458
1458
But they should know that doing so *introduces* the inverse bug for the frontends that do not have this bug.
1459
1459
1460
+
As an example, use a python3 kernel and evaluate ``𨭎𨭎𨭎𨭎𨭎 = 10``. Then type ``𨭎𨭎`` followed by the tab key and see if it properly completes.
1461
+
1460
1462
Known affected frontends (as of 2017-06):
1461
1463
1462
1464
- Jupyter Notebook < 5.1
1463
1465
- JupyterLab < 0.24
1464
1466
- nteract < 0.2.0
1465
-
- CoCalc
1466
1467
- Jupyter Console and QtConsole with Python 2 on macOS and Windows
1467
1468
1468
1469
Known *not* affected frontends:
1469
1470
1470
-
- QtConsole, Jupyter Console with Python 3 or Python 2 on Linux
1471
+
- QtConsole, Jupyter Console with Python 3 or Python 2 on Linux, CoCalc
0 commit comments