txtyash / helix_plugins Goto Github PK

If there's a preexisting plugin with a name suited to that editor such as "vim-move" then these names should be edited to something new like "helix-move", "helix-transport", etc.

Basically, anything with a name with helix in it or a new suitable name.

https://github.com/easymotion/vim-easymotion

WakaTime

Description: Send Helix usage statistics to WakaTime.

Issues: Not an issue anymore but small discussion here.

References:

• This is possible in not only bulky IDEs like VS Code etc but also other terminal-based modal text editors like Vim, NeoVim and Kakoune - see here.
• Wakatime plugin guidance here.

Implementation: Plugin

MUcomplete

• Description: Autocompletion
• Issues/Discussions: helix-editor/helix#1063, helix-editor/helix#901, helix-editor/helix#1015
• References: https://github.com/lifepillar/vim-mucomplete
• Implementation: Built-in preferred.

It feels contra productive to first create an issue ( like #2 ) and then duplicate that work in a merge request.

Better would be to immediately create a merge request ( like #4 ).

This issue can be solved by updating the Contributing section of the README.md.

helix-remote-development

• Description: Seamlessly edit code from ssh host machine
• Issues: helix-editor/helix#3721
• References: https://code.visualstudio.com/docs/remote/remote-overview
• Implementation: Plugin

I tried sshfs and running helix on remote machine but both suffered from lags, would be awesome if it is possible to achieve user experience for remote development similar to vscode have