voldikss / coc-cmake Goto Github PK

Hello,

this plugin seems to work better. Maybe integrate this and choose between vs.code.cmake and this can be nice (as coc-python)

on latest commit
running yarn install --frozen-lockfile :

[1/5] Validating package.json...
warning [email protected]: The engine "coc" appears to be invalid.
[2/5] Resolving packages...
warning [email protected]: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
error Your lockfile needs to be updated, but yarn was run with `--frozen-lockfile`.

i tried with just yarn install but got a error when compiling webpack : https://pastebin.com/8uc5WXaP

thanks

:ref: is not rendered, like :ref:cmake-language in the picture

Not sure, but I think this could be very easily achieved with:

@@ -40,7 +40,7 @@ export default class CMakeFormattingEditProvider
 
 async function format(document: TextDocument, range?: Range): Promise<string> {
   const formatter = getConfig<string>('formatter')
-  const args = []
+  const args = getConfig<Array<string>>('formatter_args')
   if (!range) {
     args.push(Uri.parse(document.uri).fsPath)
   } else {

This however has not been implemented, I am sure there is a reason for that?..

Otherwise I could totally do a pr, please lmk;

Thanks!

I just installed the extension (version: 0.0.2) using

:CocInstall coc-cmake

and put the configurations in the coc-settings.json. I have also checked whether the extension is activated.

Is there any step I'm missing / doing wrong?

Ref:

1. vscode-cmake-tools debug
2. coc-rust-analyzer vimspector support
3. does clangd support codelens run? which gives instruction on some test items, I'm not sure at all
4. example vimspector config based on CodeLLDB

   {
           "c/c++ - launch": {
           "adapter": "CodeLLDB",
           "configuration": {
               "request": "launch",
               "program": "${workspaceRoot}/${fileBasenameNoExtension}",
               "stopAtEntry": false
           },
           "breakpoints": {
               "exception": {
                   "cpp_throw": "Y",
                   "cpp_catch": "N"
               }
           }
   }

5. vscode-cpptools-integration

This plugin is awesome and works perfectly, but it can't show documents for capital keywords.

• Works
  
• Doesn't work
  

maybe we could integrate some functionnality from this tool.
It seems to have a linter and a formatter

It would be pretty amazing if something could parse CMake syntax and communicate highlight regions for the plugin. Right now highlighting is done based on syntax file, which is 1) often out-of-date, 2) good enough for standard CMake code, but only introduces confusion when used in custom CMake code, e.g.: