Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
This repository was archived by the owner on Aug 1, 2021. It is now read-only.

vim-denops/denops-spec

Open more actions menu

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 

Repository files navigation

Denops specification

Denops is an ecosystem of Vim and Neovim to write plugins in Deno.

Architecture

Denops runs two server processes named "Channel" and "Service". The "Channel" server translate stdin/stdout to TCP connection. The "Service" server translate Denops RPC to corresponding protocol of Vim/Neovim and it holds all plugins as worker threads.

Architecture

FAQ

Why do we need "Channel" layer

Without "Channel" layer, we cannot use console.xxx()(e.g. console.log()) to print messages while those messages are written into stdout which is used to communicate with Vim/Neovim. It is quite unusual behavior for general Vim plugin developers who don't really familiar with Vim/Neovim's RPC mechanisms. That's why we decided to add the "Chanel" layer to allow developers to use console.xxx() for debug printings.

Why do we use worker threads to run plugins

The initial version of denops run each plugins as separated processed but

  • Running plugins as processes cost too much for users who install tons of plugins
  • It's much simple to manage only the service server process rather than manage each plugins individually

So at least for now, each plugins are executed on isolated worker threads.

About

Denops specifications

Resources

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published
Morty Proxy This is a proxified and sanitized view of the page, visit original site.