jerry40
en-dash character prevents output from displaying.
I'm using commit f25fb90b95529b17a006a807bd04e6aee12ea304 as built and installed by guix.
In a jupyter notebook with the guile kernel, add the following code to different cells:
(display "display function works")
(display "\u2013")
(display "hello")
Run all cells. The first cell produces the expected output, but the second and third cell don't produce output even though they show the output number. When all cells are run again, no cell produces any output, but the output count is shown.
The escaped unicode can be replaced with the actual en-dash character "–" for the same results.
I have not tried this with other 16-bit unicode character codes.
guile itself can run all of the above code as expected.
This issue is not present in the python kernel. The code blocks:
print("print function works")
print("\u2013")
print("hello")
work as expected.
This is most likely a problem with how the guile kernel handles the jupyter protocol.
Attached is issue.ipynb.gz which replicates this issue with the guile code above.
Did a little investigation. I tried mimicking the behavior on this line and found that it likewise doesn't display anything. This could be a guile problem after all. Can I get a second opinion?
Nevermind that last comment. I didn't see the output because I didn't include a new line character.
scheme@(guile-user)>
(eval (with-input-from-string "(display \"\u2013\n\")" read) (interaction-environment))–
So I guess this is a valid issue.
Hi @jgibbons94 , thanks for the message!
I tried to reproduce it and it worked on my side. It is the latest master executed in the docker image. I used Firefox 89.0.1 for testing it.
Could it be a browser issue? Is it possible for you to test the master branch (using the docker) to understand the issue better?
I'm afraid it will be a bit difficult to test using docker atm. But I can confirm it is not a browser issue because this happens with both ungoogled chromium 91.0.4472.114 and icecat 78.11.0esr. If this issue cannot be replicated in a docker image, perhaps it's a problem with how guix builds it. I'll bring this up with the guix maintainers and see if they can help me sort it out.