[Feature] Any chance in making this a standalone package?

weirongxu / coc-explorer

📁 Explorer for coc.nvim

MIT License

1.14k stars 45 forks source link

[Feature] Any chance in making this a standalone package? #572

Open elzii opened 1 year ago

elzii commented 1 year ago

I've almost completely moved off CoC, making nvim less of a memory hog. Long and arduos process, yet...

Literally nothing tops CoCExplorer for me. Not CHADTree, NeoTree, Oil, Fern, NetRW, nada.

Neotree comes the closest but i strongly dislike the search functionality compared to CocExplorer.

Is there something that makes this heavily dependent on CoC? Haven't perused the code heavily yet.

weirongxu commented 12 months ago

The core code can be reused, but some user layer areas depend on coc.nvim

JSON configuration (based on coc-settings.json)
Search Interactive (based on CocList)
API: Highlight, Key mapping, Buffering list

I think part of the API can be replaced by neovim node-client, but it requires some extra adaptation code.

But you'd have to write a CocList like function to simulate the current search experience.

elzii commented 9 months ago

Not too huge a scope, not very small either. I'll try my hand. CocExplorer is by far the best explorer/sidebar. no new paradigms to learn, better then competitors like Neotree. Good ya either way mate. Cheers