Frédéric Bour

@avsm: Flow copyright is copied there (with the path to MIT LICENSE updated) https://github.com/ocaml/merlin/pull/908/files#diff-1ead05ed940a205c93fcfead82ab8caeR36

Thanks for listing these errors. I think #5068 already provides a decent error message, but #7858 is new to me. I will look at both in January :)

More cases: - https://github.com/ocaml/ocaml/issues/10700 - https://github.com/ocaml/ocaml/issues/11108

> Here's a classic, caused by confusing the two `let`-forms: https://discuss.ocaml.org/t/syntax-error-on-in/12297 (if nothing else, it would be nice to confirm that it is handled nicely) Nice variation that I missed....

Hi, The existing protocol does the job quite well, and it allows for cheap experimentation with Vim/Emacs. It would not make sense to remove it in my opinion, but adding...

No it doesn't, but it is possible in principle. It is a bit involved so I won't do that anytime soon, but the plan is roughly: 1) Parse PDF annotations....

Hello, I don't have the time nor the knowledge to add support for vscode myself. However I can provide help if someone works on that. I think the easier would...

If you want to save the rendered pixels, this can be done at the OpenGL level, for instance using `glReadPixels`. When using SDL, the right function might be (I haven't...

Hi, @danisfast, sorry, my answer is incomplete and probably incorrect anyway, `SDL_RenderReadPixels` doesn't define what happens when an OpenGL context is used. Your best bet might be to use `glReadPixels`...

What happens is that Wall renders to an "OpenGL context", which is a global (or thread-local) object maintained by the OpenGL library. This context has a notion of "target" to...