Ulysse
Ulysse
~~I think you can restrict the sample testing to `type-enclosing`, `locate` and `occurrences`.~~ ~~Also, it looks like it would be painful to promote the results manually (and this happens quite...
Thanks for the report, I was able to reproduce the issue.
I don't think this is an issue with `-short-paths`. The type of `Core.Filename.dirname` really is `Base.string -> Base.string`: https://ocaml.org/p/core/v0.16.0/doc/Core/Filename/index.html#val-dirname Since `Base` is not opened there is no reason for short...
In my attempt I was able to get the short paths by doing: ``` open Base open Core let _ = Filename.dirname ```
The buffer opens only when asking for the type of a module if I am not mistaken. I don't think this as been modified recently ?
Yes, `ctrl-d` is the normal way to end the command since Merlin is waiting for the content of the buffer to be provided on standard input. But sending SIGINT should...
> ```$ cat my_file.ml | ocamlmerlin single errors -dot-merlin .merlin | jq``` Yes, piping the file's content to Merlin is the correct way to use the cli. A command such...
Thanks Rafal !
Yes, these warnings have always been disabled in Merlin: https://github.com/ocaml/merlin/commit/1f1fee1ed6e08cede167d00130e42a9646dff7f5 https://github.com/ocaml/merlin/blob/1f1fee1ed6e08cede167d00130e42a9646dff7f5/src/ocaml/typer_403/utils/warnings.ml#L207-L208 I always assumed that the reason was to not bother the user while writing code since most values start...
Looks like a configuration problem ? Any VIM user around ? Maybe @julow ?