Type Providers which output to stdout can hang the Atom mode

[donald-pinckney]

If a type provider outputs stuff to stdout (during type checking), this output is then inserted into the ide-mode stdout stream which the Atom mode is reading. This messes up the parsing of the ide-mode output, presumable since then message length are no longer correct. Not sure if its possible to fix it here in the Atom mode, or if it needs to get fixed in Idris.

[justjoheinz]

If the emacs mode messes this up as well, it should be idris fault. Can you test this?

[david-christiansen]

This was actually the motivation for having the Emacs mode talk over a socket, and then display stdout and stderr in a buffer.

…

On Mon, May 18, 2020, 08:34 Markus Klink ***@***.***> wrote: If the emacs mode messes this up as well, it should be idris fault. Can you test this? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#245 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA4FAVHHAIBBMBVIQYDHVLRSFIQFANCNFSM4NDDO3NQ> .

[justjoheinz]

@david-christiansen How does the protocol work? I start an idris process as usually and it spits out a port number on stdout, to which I connect with a socket. And the communication via the socket is then using the standard ide protocol whereas the process might still print to stdout/stderr?

[david-christiansen]

That's exactly right. If the type provider is calling C functions then there's no easy way to keep its fingers out of stdout. So IIRC I put the Idris process buffer into a mode where it's nice for the user to interact, and then run the protocol over the socket.

…

On Tue, May 19, 2020, 00:18 Markus Klink ***@***.***> wrote: @david-christiansen <https://github.com/david-christiansen> How does the protocol work? I start an idris process as usually and it spits out a port number, to which I connect with a socket. And the communication via the socket is then using the standard ide protocol whereas the process might still print to stdout/stderr? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#245 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA4FAXQMBUOKKNXBKOPOU3RSIXFVANCNFSM4NDDO3NQ> .