https://github.com/tjdevries/rofl.nvim

Rust On the FLY completion for neovim
https://github.com/tjdevries/rofl.nvim

Last synced: about 2 months ago
JSON representation

Rust On the FLY completion for neovim

• Host: GitHub
• URL: https://github.com/tjdevries/rofl.nvim
• Owner: tjdevries
• Created: 2021-01-29T03:43:36.000Z (over 3 years ago)
• Default Branch: master
• Last Pushed: 2021-02-19T05:48:32.000Z (over 3 years ago)
• Last Synced: 2024-07-24T21:13:03.698Z (2 months ago)
• Language: Rust
• Size: 60.5 KB
• Stars: 64
• Watchers: 9
• Forks: 2
• Open Issues: 6
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml

Awesome Lists containing this project

README

        
# rofl.nvim

Rust On the FLy completion engine for Neovim.

## Why Rust?

It's 2021. I think the question you should be asking yourself is "Why NOT Rust?!?? (btw)"

## Goals

- [ ] All configuration should be done on the Lua side of things.

    - I will pretend vimL doesn't exist as much as possible at the moment.

    - All completion is done via functions. I don't like variables. They are hard to deal with.

- [ ] Able to add completion sources via Lua

- [ ] Able to add completion sources via Rust (I don't know if this is possible, but it seems cool)

    - [ ] Related to this might be the ability to add things via any remote plugin... idk.

- [ ] Snippets & related expansion

    - I don't know how complicated we'll get with these, but I want to do some stuff with snippets so that I can figure out how we can implement the right stuff in Neovim core :)

- [ ] Builtin sources

    - [ ] Builtin LSP

    - [ ] Buffer

        - [ ] Fuzzy buffer completion with bonus points for being close to the cursor

    - [ ] File

    - [ ] ... your ideas here

    - [ ] Can we bundle neovim, access the C codes for some completion sources and use them "async"-y from neovim itself...?

        - Could be a fun project for messing around with C & Rust interop.