Live Share Plugin for Neovim

Плагин Neovim для совместного редактирования в режиме реального времени.

Он функционирует только между экземплярами Neovim и не совместим с Live Share в Visual Studio Code.

Для работы плагина необходим SSH, он протестирован на Linux и OpenBSD, но не поддерживается на macOS и Windows.

src: https://github.com/azratul/live-share.nvim

#opensource #github #vim #nvim #neovim #neovimplugin #liveshare

GitHub - azratul/live-share.nvim: Creates a "Live Share" server in Neovim, similar to the Visual Studio Code Live Share functionality

Creates a "Live Share" server in Neovim, similar to the Visual Studio Code Live Share functionality - GitHub - azratul/live-share.nvim: Creates a "Live Share" server in Neovim,...

GitHub

Been using #vscode #liveshare again for 🍐 'ing - forgot how much better than sharing a screen in zoom

If you pair program a lot and haven't tried it, it's worth a go: https://code.visualstudio.com/blogs/2017/11/15/live-share

Introducing Visual Studio Live Share

Real-time collaborative development

@itsfoss

#ZedEditor can drag #VSCode #LiveShare through the mud, if everything is #CRDT-first and it really works fast. (Had terrible desynchronization on VSC part.) To seriously consider it in enterprise, though, first major release needs to happen with collab tools already available as a #SelfHosted solution (not just their cloud that you can't be sure to be 100% secure and available 24/7). You can set custom `server_url` in settings (as user) and deploy `collab` crate (as devops), but authentication is another step that you have to band-aid, at the moment.

Overall, I don't expect much besides advertised features during the beta, which include fast autocompletion and language-agnostic tree, so it's a winner.

#Zed #ZedIDE #VisualStudioCode #LiveCollaboration #PairProgramming #LSP

@dch it is! Actually, #LiveShare and trivial #LSP setup was the reason I switched to #VSCode in #VI mode as my primary editor. Since then I have set up #NeoVIM to have #LSP integration and sometimes code in it, but #VSCode is a surprisngly solid and memory-efficient piece of software.

@dch #GNUScreen was the closest. In #tmux you couldn't drive separate panes / windows, whereas in #Screen there are `:acladd $USERNAME` to share a socket with another user and the default behaviour is that an active window is personal per user connected.

I used to use GNU Screen for pair programming, but #LiveShare is truly revolutionary. I think that it's less of a hardware proceedings and more so proceedings in practical implementations of conflict-free data structures.

Had some quality time with a couple #cslanet users last week on a Teams meeting. They'd discovered a bug and had done a lot of research to narrow down the behavior.

In about 3 hours via #teams and #liveshare in #visualstudio we were able to fix the bug in version 7 and the upcoming version 8. So much fun to collaborate like that!

#oss

A very interesting session from the M365 & Power Platform community! @davrous shows how to build a collaborative Metaexperience using Teams and the Live Share SDK https://www.youtube.com/watch?v=-HCnIhpu2zE #MicrosoftTeams #Metaverse #LiveShare
Building Metaverse experiences using Teams LiveShare SDK

YouTube

@Moke @TimPurdum it is amazing isn't it!?!

I use it for coding, but also when authoring markdown in #vscode, where it is extremely helpful to create docs.

We used it in a #LiveShare brainstorming session recently (a bunch of us editing the same md file) and it was almost like having another team member who could draw from Wikipedia, etc. without us having to manually do the searching!