Enrico Sada

> check for the host OS to see if it's WSL exactly. dunno :D. fsac will be a windows process, running on windows (probably), but started from WSL linux.. so...

Another way, instead of make it more generic, is to support multiple formats in FSAC, based on an initialize config. like: - `signature: Markdown | PlainText` - `signatureLinkTemplate: string` so...

What is a format nice output for: - vim ( @cannorin ) - emac ( @TOTBWF ) i think this will be useful also in other places, for rich text...

@cannorin i mean, the idea is to format to plaintext too, but if vim has a special way to use stuff like link, bold, etc, we can format like that

@kjnilsson the fsac is a zombie issue can be fixed with new fsac argument `--hostPID` (ref https://github.com/fsharp/FsAutoComplete/pull/190 ) So fsac will terminate itself if the vim process who started it...

@mrward i checked and i can repro. But i prefer try to not disable defaults (`EnableDefaultItems`) if possibile, because it mean duplicate that logic (like for `Resource`) and that mean...

👍 for `forge`, reuse is awesome :D

how to fix it: we need to implement F# support in `WriteCodeFragment` tasks https://github.com/Microsoft/msbuild/blob/master/src/Tasks/WriteCodeFragment.cs is just a foreach over assemblyattributes, in the switch (for coreclr), like [c# does](https://github.com/Microsoft/msbuild/blob/2e302ddec9dab44f5f71993b2e5eaa67d7a58310/src/Tasks/WriteCodeFragment.cs#L294-L313), no codedom...

i dont want to vote because is mine, but `ProjectCracker` has many drawback (in process, known stackoverflow, depends on msbuild libs not always avaiable and special env var to set,...

any issue with project parsing, anyone, feel free to ping me directly