Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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. #468

Merged
merged 2 commits into from
Aug 19, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/messaging.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1457,17 +1457,18 @@ 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
- 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::

Expand Down