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
Functions that involve multiple calls to print, println, (.Write ^TextWriter w "bla"), etc – basically anything that writes to *out* in multiple steps – are prone to print to the emacs repl in a garbled form, with newlines inserted and removed seemingly at random. This makes data almost unreadable. For example, the following:
(pprint
(let [f (fn f [i]
(if (<= i 0)
:leaf
(vec
(repeatedly3
#(f (dec i))))))]
(f4)))
Does the same thing happen if you use the standard read function? It seems similar to the issue where the repl gets stuck, which doesn't happen when you use the standard read function (as described in #292).
Functions that involve multiple calls to
print
,println
,(.Write ^TextWriter w "bla")
, etc – basically anything that writes to*out*
in multiple steps – are prone to print to the emacs repl in a garbled form, with newlines inserted and removed seemingly at random. This makes data almost unreadable. For example, the following:prints as:
In Nostrand it evidently prints as
Among other things, this could be:
This is a fairly major issue because it makes complex data unreadable.
The text was updated successfully, but these errors were encountered: