Roadmap for v0.1 #9

chemzqm · 2018-07-18T02:03:34Z

iamcco · 2018-07-19T16:13:01Z

is it possible to support code block detection like ncm2 with ncm2-markdown-subscope ?

chemzqm · 2018-07-20T03:08:40Z

@iamcco There is a plan for something like that, but not high priority for now.

kdurant · 2018-08-04T13:59:16Z

Can use it on Win10？

chemzqm · 2018-08-04T15:19:29Z

@kdurant it works on my win7, should works on win10 as well.
BTW, there's some issue with vim, using neovim should be fine.

fannheyward · 2018-09-17T11:30:09Z

Microsoft's python-language-server is just released: https://github.com/Microsoft/python-language-server

According to https://github.com/Microsoft/vscode-python/blob/master/src/client/activation/languageServer.ts#L159, the VSCode-python can download LS bin.

sandangel · 2018-10-27T15:32:15Z

could you please consider adding emmet support? so I could use Tab to expand html markup without conflict with coc auto-complete

	" Use <Tab> for confirm completion.
	" Coc only does snippet and additional edit on confirm.
	inoremap <expr> <Tab> pumvisible() ? "\<C-y>" : "\<Tab>"

chemzqm · 2018-10-27T17:13:33Z

@sandangel you just need to extend the remap, like:

  let g:user_emmet_leader_key = '<C-e>'
  let g:user_emmet_expandabbr_key = '<C-x><C-e>'
  imap <silent><expr> <Tab> <SID>expand()

  function! s:expand()
    if pumvisible()
      return "\<C-y>"
    endif
    let col = col('.') - 1
    if !col || getline('.')[col - 1]  =~# '\s'
      return "\<Tab>"
    endif
    return "\<C-x>\<C-e>"
  endfunction

Notice imap is used here so that you can't let emmet use the mapping for <C-y>

sandangel · 2018-10-28T01:24:41Z

thanks @chemzqm for your tip. However, I mean it would be great if we can add emmet to completion source and only have to use Tab to expand it. With the above tip, we can only expand emmet after close the popup menu.

chemzqm · 2018-10-28T05:23:43Z

thanks @chemzqm for your tip. However, I mean it would be great if we can add emmet to completion source and only have to use Tab to expand it. With the above tip, we can only expand emmet after close the popup menu.

I don't understand how could this work, provide a complete item with label like expand emmet or just expand the complete item if it's confirmed and is not snippet?

sandangel · 2018-10-28T05:33:37Z

I mean is it posible to add emmet suggestion to the popup menu like vscode?

chemzqm · 2018-10-28T05:46:26Z

~~It's possible by create a custom source, but I don't think it's useful since you can always expand emmet with it's own expand key, and it could be buggy.~~

adelarsq · 2018-11-07T14:10:48Z

@chemzqm Any idea if VS Code Debug Protocol will be supported?

chemzqm · 2018-11-07T15:00:12Z

@adelarsq I've thinked about it, but one big problem is I don't know how to make it easy to use, ex: I can't create buttons in terminal vim.

adelarsq · 2018-11-07T17:48:56Z

@chemzqm We can take ideas from vim-vebugger. About buttons, we can use denite or quickmenu to provide "buttons".

aeosynth · 2018-11-07T19:39:04Z

there are a bunch of vim debuggers to look at for ideas, here's one which even uses the debug protocol (i haven't used it): https://github.com/puremourning/vimspector

chemzqm · 2018-11-14T12:41:33Z

I've experienced with emmet completion in VSCode, I think it's worthy to have it, since it would help to reduce the number of key stroke you need to use for snippet.

adelarsq · 2018-11-14T14:35:17Z

@chemzqm Would be nice. Actually I use emmet-vim with <c-e> as leader key.

Moroxus · 2018-12-19T10:17:01Z

Is it possible to add semantic highlighting through LSP protocol?

chemzqm · 2018-12-19T17:42:18Z

@Moroxus LSP don't have semantic highlight yet, but it's possible for coc to implement.

ovidius72 · 2018-12-28T18:26:18Z

Is it possible to add icons in the completion menu, similar to vscode, that distinguish methods, property and snippet ?
It's not just an aesthetic matter, it would be helpful to easily find the correct item.
Like in this comment #9 (comment)

Thanks.

oblitum · 2018-12-28T18:40:52Z

@ovidius72 it's possible, through what is available in Unicode and font with colored characters/emoji (plus terminal support of that if you're on terminal), or custom fonts. There's no option for enabling or tweaking that in coc though.

ovidius72 · 2018-12-28T21:56:39Z

Thanks @oblitum
I'm on terminal. I have nerd fonts working fine but unfortunately have no idea where to start.
I joined the vim word only a few weeks ago.
Can you suggest any tutorial or doc where I can start from ?

oblitum · 2018-12-28T22:07:16Z

@ovidius72 hi, I just meant that it's not impossible, since you can use emoji/unicode/custom-fonts for that, but coc.nvim doesn't provide options for tweaking kind or other parts of the menu, which may vary depending on language, that's up to @chemzqm or your willing to fork/patch it to put Unicode in it.

oblitum · 2018-12-28T22:10:50Z

@ovidius72 you would put your emoji around here: https://github.com/neoclide/coc.nvim/blob/master/src/util/complete.ts#L72

oblitum · 2018-12-28T23:07:55Z

@ovidius72, for example:

cd ~/.vim/plugged/coc.nvim

@@ -74,7 +74,7 @@ export function completionKindString(kind: CompletionItemKind): string {
     case CompletionItemKind.Text:
       return 'Text'
     case CompletionItemKind.Method:
-      return 'Method'
+      return '📙'
     case CompletionItemKind.Function:
       return 'Function'
     case CompletionItemKind.Constructor:

yarn install
nvim sample.cpp

ovidius72 · 2018-12-29T01:13:03Z

@oblitum Wow this is nice.
I'll take a look at it as soon as possible. Is it also possible to show them at the left side ?
Thanks.

oblitum · 2018-12-29T01:15:07Z

@ovidius72 anything is possible, since it's open source, good luck maintaining the patch though.

oblitum · 2018-12-29T01:17:46Z

@ovidius72 the kind of the completion is generally shown in the middle though, never left-side, it's the way Vim does things, you could try patching it for that but you would be really going against how Vim works, to the point you better stick to vscode.

ovidius72 · 2018-12-29T01:25:23Z

@oblitum ok, I understand that make sense.
And no, i will not give up for this, I'm getting comfortable with vim now and you want me to switch back to vscode for a few icons ;-)

theFool32 · 2018-12-29T06:42:57Z

I find the repo coc-jedi, does it conflict with the integration of Microsoft/vscode-python?

BTW, what's the difference between the sources (vim plugins?) and extensions (node package?). I'm new to coc.nvim and vimL, and wonder whether there exist a fast and easy way to port something like ncm2-tmux, ncm2-look and ncm2-en to coc.nvim.

Thanks.

chemzqm · 2018-12-29T06:59:49Z

does it conflict with the integration of Microsoft/vscode-python?

They could work together, but you may have duplicated complete items.

what's the difference between the sources (vim plugins?) and extensions (node package?)

Coc load sources from viml plugin as extension internally, the source could be implemented in viml as vim plugin, or javascript as node package. The call to viml function could quite slow, and block your typing, so it's recommended to use node module, and it could make use of javascript APIs from coc.

whether there exist a fast and easy way to port something like ncm2-tmux

Not yet, but possible in the feature.

kutsan · 2018-12-31T19:29:42Z

A way to change location and name of coc-settings.json file?

oblitum · 2018-12-31T19:41:40Z

@kutsan you can use configuration from .vimrc and ditch coc-settings.json, check :h coc#config(), example.

kutsan · 2018-12-31T20:08:49Z

@oblitum Oh, thanks; that was what I wanted in the first place.

oblitum · 2019-01-02T21:44:21Z

@kutsan fyi, updated example, due to breaking changes.

oblitum · 2019-01-03T01:23:02Z

@kutsan fyi, updated example, due to breaking changes.

FWIW, I think all plugin specific global variables should be prefixed with the plugin name, and g:rooter_patterns should have been called g:coc_root_patterns instead (besides following docs regarding implementation).

chemzqm · 2019-01-03T15:26:41Z

I've removed using of g:rooter_patterns, it's bad idea, new setting coc.preferences.rootPatterns also added.

sandangel · 2019-01-03T15:46:03Z

@chemzqm I think you also need to change the coc.txt file as well

g:rooter_patterns 				*g:rooter_patterns*

			To specify how to identify a project's root directory >

			let g:rooter_patterns = ['Rakefile', '.git/']
<

			default to `['.vim/', '.git/', '.hg/', '.projections.json']`

			Note: you can specify different project root for
			language servers by use `rootPatterns` in
			settings.json.

rbpatt2019 · 2019-02-15T14:23:07Z

Thanks for the great work @chemzqm! I've found pyls to be a bit of a pain and look forward to coc.nvim with the Microsoft Python extension!

kabouzeid · 2019-04-10T13:00:50Z

I find the repo coc-jedi, does it conflict with the integration of Microsoft/vscode-python?

BTW, what's the difference between the sources (vim plugins?) and extensions (node package?). I'm new to coc.nvim and vimL, and wonder whether there exist a fast and easy way to port something like ncm2-tmux, ncm2-look and ncm2-en to coc.nvim.

Thanks.

@theFool32 I've just added support for coc.nvim in tmux-complete (wellle/tmux-complete.vim#84)

oblitum · 2020-01-14T19:49:51Z

Hello.

The current state is rather confusing for coc.nvim, as there isn't release tags anymore since 08/2019 and compiled state is being pushed to the release branch since then. Given that, does this issue represent anything yet? Should it be closed or is there still plans for reaching 0.1?

chemzqm · 2020-01-15T02:17:20Z

Need lots of tests, but I don't have too much time recently.

carlosala · 2021-11-12T08:55:45Z

Is there going to be a new release? I saw that this issue seems a little bit abandoned. Should we use directly master or just wait for release be updated (talking about production, of course)

oblitum · 2021-11-12T11:10:46Z

@carlosala the release branch, as instructed from readme, doesn't require compilation from user. Each commit in that branch is a release.

chemzqm added this to the v0.1 milestone Aug 1, 2018

chemzqm self-assigned this Aug 1, 2018

neoclide blocked kdurant Aug 23, 2021

Roadmap for v0.1 #9

Roadmap for v0.1 #9

Comments

chemzqm commented Jul 18, 2018 • edited

iamcco commented Jul 19, 2018

chemzqm commented Jul 20, 2018

kdurant commented Aug 4, 2018

chemzqm commented Aug 4, 2018 • edited

fannheyward commented Sep 17, 2018

sandangel commented Oct 27, 2018

chemzqm commented Oct 27, 2018

sandangel commented Oct 28, 2018 • edited

chemzqm commented Oct 28, 2018

sandangel commented Oct 28, 2018

chemzqm commented Oct 28, 2018 • edited

adelarsq commented Nov 7, 2018

chemzqm commented Nov 7, 2018

adelarsq commented Nov 7, 2018 • edited

aeosynth commented Nov 7, 2018

chemzqm commented Nov 14, 2018

adelarsq commented Nov 14, 2018

Moroxus commented Dec 19, 2018

chemzqm commented Dec 19, 2018

ovidius72 commented Dec 28, 2018

oblitum commented Dec 28, 2018 • edited

ovidius72 commented Dec 28, 2018

oblitum commented Dec 28, 2018

oblitum commented Dec 28, 2018

oblitum commented Dec 28, 2018

ovidius72 commented Dec 29, 2018

oblitum commented Dec 29, 2018

oblitum commented Dec 29, 2018

ovidius72 commented Dec 29, 2018

theFool32 commented Dec 29, 2018

chemzqm commented Dec 29, 2018 • edited

kutsan commented Dec 31, 2018 • edited

oblitum commented Dec 31, 2018

kutsan commented Dec 31, 2018

oblitum commented Jan 2, 2019 • edited

oblitum commented Jan 3, 2019 • edited

chemzqm commented Jan 3, 2019

sandangel commented Jan 3, 2019

rbpatt2019 commented Feb 15, 2019 • edited

kabouzeid commented Apr 10, 2019 • edited

oblitum commented Jan 14, 2020 • edited

chemzqm commented Jan 15, 2020 • edited

carlosala commented Nov 12, 2021

oblitum commented Nov 12, 2021

chemzqm commented Jul 18, 2018 •

edited

chemzqm commented Aug 4, 2018 •

edited

sandangel commented Oct 28, 2018 •

edited

chemzqm commented Oct 28, 2018 •

edited

adelarsq commented Nov 7, 2018 •

edited

oblitum commented Dec 28, 2018 •

edited

chemzqm commented Dec 29, 2018 •

edited

kutsan commented Dec 31, 2018 •

edited

oblitum commented Jan 2, 2019 •

edited

oblitum commented Jan 3, 2019 •

edited

rbpatt2019 commented Feb 15, 2019 •

edited

kabouzeid commented Apr 10, 2019 •

edited

oblitum commented Jan 14, 2020 •

edited

chemzqm commented Jan 15, 2020 •

edited