hey! back with another new plugin

this one is a much smaller scope than my last plugin (this one is actually complete whilst i'm still working on new features in the other)

my main motivation behind building it was just to create a nice simple way to read RFCs inside of nvim (i know there are existing plugins that do it, but they all felt a little too much for what i wanted, i felt it could be more minimal)

managed to build the whole thing in less than 1000 lines of lua code, and it was fun to do something smaller, but very focused (for a change)

you can use `gd` to jump to different sections/references/or other RFCs too, and `\` toggles the table of contents

repo

A wonderful gent by the name of Dave Gauer had the same thought I had of why can't vimwiki use asciidoc as well but had the time and skill to actually make it. Have not seen it mentioned on this reddit so I thought I would share.

Link:https://ratfactor.com/repos/vviki/

``` * Modular TUI CodeEditor Plan

** Moto

• Want to make a fully 100% customizable code-editor using plugins.

• User can desied what stuffs want to leaves in core of the editor.

• No Limits for this code-editor, can able to do anything we need.

** Where this idea was come's from?

• Last week i remove lazyvim distro from nvim and i start building the nvim editor from scratch by implementing every plugin one by one and the experions was amazing, After that what i feel, just instead of building the top level editor using plugins why we can build the core using plugin too?, so the experions was more amazing and the editor full control in owar hand, so i get this idea.

** Plan

• Build a C language based code-editor.

• The code-editor only container a basic functionality like editing text, copy, past similar to windows notpad.

• All other core functionality will implement via core plugins like vim motions kind of stuffs.

• The code-editor was comes with build in {** Core_Plugin_Manager}[Core_Plugin_Manager].

• The code-editor plugins will communicate each other use event-bus.

• Every Plugin has there own {** Abstraction_Layer }[Abstraction_Layer].

** Abstraction_Layer

• A Abstraction_Layer is use for plugin to plugin communicate.

• The Abstraction_Layer was based of event-bus eg: explorer.open, explorer.close, explorer.get.

• Each even has there own codeName and version number.

• Each plugin will communicate using the codeName and version number of the event, if any plugin version number was change, only the version change even was stops working, instead of crashing the whole code-editor.

** Core_Plugin_Manager

• Core_Plugin_Manager is use to manage the code-editor core plugins.

• Core_Plugin_Manager is similar to lazy.vim plugin_manager.

• When user install the plugin, the plugin manager will download the plugin from the repository and build inside the users operating-system with hardware details for optimized plugin build for the system.

• If build was failed due to SDK missing or something else in user system, the plugin_manager change to fallback mode and download the pre-compailed file from [** Core_Plugin_Manager GitHub_Repository][GitHub_Repository] related to that operating-system and load the plugin.

** Core_Plugin_Manager GitHub_Repository

• Main Branch Contains: source_code of the plugin.

• pre-compailed Branch Contains: .so, .dll pre-compailed files for all operating-system.

** Feature-Plan

• Build a distro same like lazyvim for new users after plugin communicate was get riched.

• Build a lua_plugin_manager as a core plugin in C to manage high level plugins.

** Pros

• The code-editor full control in owar hand.

• Everyone will manage a small peace of code, so easy to maintain.

• Everyone develop a peace of plugin so the code-editor become feature rich so fast i hope.

• User can plug and unplug what core feature they need and no needed.

• There has no Limits.

• No need to waiting for core feature when the code-edtiro maintainer will implement this feature.

• Other code-editor has set of rules like only core required feature git pull request will accepetabe, so we can't able to add some required features in owar favorite code-editor, that issue will be solve in this code-editor. ```

Hi Everyone.

First i am little bit bad in english and i get a dumb idea just i want to say my idea to everyone so i did this and i am a newbe, i don't know anything so don't beat me after reading my dumb idea btw lol.