Cannot load Coc Extension only in MacVim

25 views
Skip to first unread message

Aaron Hayman

unread,
Sep 14, 2022, 9:54:01 AM9/14/22
to vim_mac
I've been using Coc for a while to handle linting/autocomplete/etc for a variety of languages.  I recently installed `coc-ltex` to handle grammar checking in markdown files. This works fine if I use vim on a markdown file from the command line. The extension activates, downloads the appropriate language server, and runs just fine.

If I open a markdown file with MacVim, nothing happens. When I check `:CocList extensions`, the extension is listed but not active.  Attempts to activate it fail with no displayed error message.  However, if I `:echo errmsg` after I try to activate the extension, I see: `E716 key not present in dictionary: "2"`, although that's not much help.

I suspect that something in MacVim is preventing the extension from downloading the language server, but I don't know what it could be.

Note: `:version` display the exact same version in both command-line vim and MacVim:

VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Jul 25 2022 08:23:03)
macOS version - x86_64
Included patches: 1-65    

Yee Cheng Chin

unread,
Sep 15, 2022, 5:50:39 PM9/15/22
to vim...@googlegroups.com
I don't have Coc installed and this plugin requires some set up. Are others seeing this as well? Can you file a GitHub issue with more detailed steps for a minimal repro? Otherwise it could be hard for me to know how to start reproducing this.

You could also consider filing an issue at coc-ltex. They should know the codebase a lot better and able to pinpoint where the issue is (or at least add a more descriptive error message). Otherwise it would be a lot more work for us to dig through things.

Other than that, it could be a permission issue. You could go to System Preferences → Security Settings → Privacy and see if there is a category where MacVim is not checked. macOS usually only asks once so if you rejected a permission before it may just be silently blocking things.

--
--
You received this message from the "vim_mac" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_mac/ad2c88dc-f592-4c05-8827-f9f4c5e381fcn%40googlegroups.com.

Yee Cheng Chin

unread,
Sep 15, 2022, 6:01:40 PM9/15/22
to vim...@googlegroups.com
Another thing that I can remember off the top of my head is to check whether this plugin works in GVim for Windows or Linux. For example, the behavior for ":!" was changed recently for (POSIX-based systems) GVim (see https://github.com/vim/vim/issues/8951) which could cause spawned background processes to immediately exit after the command is done (compared to terminal Vim where it would run in the background). If coc uses that command to spawn processes (and don't check the results) that could make a difference between terminal and GUI Vim.
Reply all
Reply to author
Forward
0 new messages