Hubert Kindermann

Perhaps we could replace our parsing with Roslyn's internal one: https://github.com/dotnet/roslyn/blob/main/src/Workspaces/Core/Portable/Shared/Utilities/DocumentationComment.cs https://github.com/dotnet/roslyn/blob/main/src/Compilers/Core/Portable/InternalUtilities/DocumentationCommentXmlNames.cs https://github.com/dotnet/roslyn/blob/main/src/Workspaces/Core/Portable/Shared/Utilities/XmlFragmentParser.cs

Looks like `CompletionService.GetChangeAsync` should solve this. Unfortunately, this would require changes to PrettyPrompt API.

When standard (=without detailed output) install ends with an error it could immediately suggest in the error message what keybindings would result in detailed output.

Haven't investigated yet, but the reason for separate issue from https://github.com/waf/PrettyPrompt/issues/39 is that this is not an issue in PrettyPrompt example app. Yes the insertion alone is slow in both...

LOL, this input is now causing stack overflow inside Roslyn. So I tried to paste it to VS and it just died.. I've checked that we are able now to...

Do you know about 'Ctrl+Enter' detailed output? It's not interactive in any way but provides more insight into the result. Although I'd like to improve it in the future.

Should be solved when #226 is done.

Also when I scroll up and then start writing (debug assert fails here) the view already goes back to the current cursor position, but there is not enough space for...

(hm, but we don't support key shortcuts with 3 parts)

Same problem here. Also `>` and `|` are escaped by `^`. I solved it by invoking powershell script instead of writing the command inline. `config.yml`: ```yml customCommands: - key: ''...