AndCake

@s3rgeym can you describe the issue in a little bit more detail? I am not quite sure what you mean by "Any but one: LSP.server". Please elaborate.

It would look a lot cleaner with the file type specific options, I agree, even if it might have to be in one line rather than a nice object. I...

Yes the LSP.initOptions being a string is good. And adding the option to read the lsp.server settings file type specific would be a good way to go and not require...

@akriegman : I researched and tested option parsing in micro a bit more (including the internals and non-documented methods) but it seems there is no means for a plugin to...

@akriegman : yes correct. What about if the path is calculated as a relative path from where the cwd is? That should keep it not much longer than it is...

I like the second solution! That would make it easy enough to implement and at the same time look nice. However, if the truncate_right is applied, I would suggest to...

I just stumbled over micro last week and found it great, but lacking an LSP client. So over the weekend I started working on an LSP client plugin here: https://github.com/AndCake/micro-plugin-lsp...

Good point! I haven't used a mac in a while. I will take a look at what alternative default shortcuts could be defined. In the meantime, you can use the...

I found the following settings to work rather ok on Mac: ``` { "Ctrl-k": "command:hover", "Ctrl-d": "command:definition", "Ctrl-r": "command:references", "Alt-Space": "command:completion" } ``` I noticed that micro itself also doesn't...

Hey @hikkidev , @akriegman - based on our discussion above, I created a new PR-43 to implement the changes accordingly. Please take a look and let me know if you...