Neovim show documentation | FSharp | Page 1

silent ether May 6, 2024, 5:23 PM

#

https://www.reddit.com/r/neovim/s/IBUx74oAwB

Explained in my reddit post, I essentially want to implement what vscode hover has in Neovim. Right now FsAutoComplete is serving only what vscode's ionide can really work with.

I want to make a pr for this to work for neovim.

What advice would you guys have to properly implement the FsAutoComplete pr? I know I'm going to have to grab the editor name from the config, check it's not vscode, etc. But I'm not sure how to implement things from the neovim side.

Thoughts?

From the neovim community on Reddit: Lsp show documentation.

Explore this post and more from the neovim community

median mist May 6, 2024, 5:28 PM

#

What type of support does vim/neovim have for formats provided by LSP? Like can it support markdown or does it have to be a custom output?

spring quest May 6, 2024, 5:33 PM

#

in general, the client (neovim) will send a structure identitfying itself as part of the initialize call to start the FSAC LSP server. you'll want to see what that value is for neovim. For Ionide it looks like this:

{
    "processId": 3560,
    "clientInfo": {
        "name": "Visual Studio Code",
        "version": "1.89.0"
    },
...
}

#

any FSAC PR would probably want to start doing some kind of pivoting of settings/default/logic based on the caller - though the 'better' way of doing those pivots would be to have some kind of config setting that could be changed based on the client

median mist May 6, 2024, 7:13 PM

#

oh I see it's a command oriented link specific for vscode

spring quest May 6, 2024, 8:47 PM

#

yeah - @median mist this is one of the things I was worried about how we'd do in the general case. This is similar to the problem we'd have with info panel trying to make it cross-editor - we don't have a good way to embed 'hey interacting with this should trigger OTHER_COMMAND' in a way that'd work in vim and vscode

buoyant loom May 7, 2024, 5:41 PM

#

we don't have a good way to embed 'hey interacting with this should trigger OTHER_COMMAND' in a way that'd work in vim and vscode

one would think this should be part of the LSP spec...

#

However I'm bit confused - @silent ether talks about hover above, but this code formatting something as HTML link is from Info Panel formatter.
I don't believe we're putting such links in tooltips - Hovers according to LSP spec supports markdown formatting

spring quest May 7, 2024, 5:55 PM

#

We have a hover link in the tooltips that opens info panel by firing the command

#

The problem is that we don't put all of the information we used to in the hovers now that we delegate to info panel - but not all editors have info panel

buoyant loom May 7, 2024, 5:59 PM

#

We have a hover link in the tooltips that opens info panel by firing the command
really? wow

#

;P

#

Ahh... yeah, it's here: https://github.dev/ionide/FsAutoComplete/blob/e9ad5ebf7ba65b906352158c2b2ec8da19539e8c/src/FsAutoComplete.Core/TipFormatter.fs#L1237

#

But why it can't be markdown link?

spring quest May 7, 2024, 6:08 PM

#

it possibly could - but then you'd need to figure out what the 'command' syntax is for the client that's calling

#Neovim show documentation