From 24d97af897d19694fd03433c09cec106cb66c2e0 Mon Sep 17 00:00:00 2001 From: William Stein Date: Fri, 16 Aug 2019 18:43:03 +0000 Subject: [PATCH 1/2] CoCalc is no longer affected by the unicode offset issue (see https://github.com/sagemathinc/cocalc/issues/1994) --- docs/messaging.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/messaging.rst b/docs/messaging.rst index bbcce27dc..18039af14 100644 --- a/docs/messaging.rst +++ b/docs/messaging.rst @@ -1462,12 +1462,11 @@ Known affected frontends (as of 2017-06): - Jupyter Notebook < 5.1 - JupyterLab < 0.24 - nteract < 0.2.0 -- CoCalc - Jupyter Console and QtConsole with Python 2 on macOS and Windows Known *not* affected frontends: -- QtConsole, Jupyter Console with Python 3 or Python 2 on Linux +- QtConsole, Jupyter Console with Python 3 or Python 2 on Linux, CoCalc .. seealso:: From ffdc1276ea5a227cc9b0a5121a1be51196b5c5aa Mon Sep 17 00:00:00 2001 From: William Stein Date: Sat, 17 Aug 2019 01:44:13 +0000 Subject: [PATCH 2/2] add an example of an astral plane unicode identifier --- docs/messaging.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/messaging.rst b/docs/messaging.rst index 18039af14..595cefac5 100644 --- a/docs/messaging.rst +++ b/docs/messaging.rst @@ -1457,6 +1457,8 @@ Frontends claiming to implement protocol 5.2 **MUST** identify cursor_pos as the 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. But they should know that doing so *introduces* the inverse bug for the frontends that do not have this bug. +As an example, use a python3 kernel and evaluate ``𨭎𨭎𨭎𨭎𨭎 = 10``. Then type ``𨭎𨭎`` followed by the tab key and see if it properly completes. + Known affected frontends (as of 2017-06): - Jupyter Notebook < 5.1