Wiki: Remote Buffer Notes


Note: You are viewing an old revision of this page. View the current version.


I hope I get all the terminology that fits with the vim application's development environment. Please bear with me, I'll update this document as I make further clarifications and distinctions. The parent of this topic is TunnelDataInCommands.

I was thinking about the implementation of a remote buffer capability. Where to draw the distinctions of what is "remote" and what is "local" would make a big difference in how this feature was implemented. My thought is that only the farthest-back layer should be remote. Here's why. I hope to learn more and either verify or change this assumption.

With a command like :remoteedit GVIM buffer1 the local user would prefer to view this data with their local settings for syntax, highlighting, local buffer variables, etc. I do not know anything about the internal vim data structure yet. My hope is that abstracting at list level is easy and/or possible without significant work.

Assuming this is implemented in this manner, each user would have their own vim-customized view of the same data that may look different on each client.

Do you have further ideas? Please append them here in a blog style with your signature.

-- GrantBow 05 May 2004


Sponsored by: Labrat Technology -- Need Consulting Services? Programming, Maintenance, Security, Database Analysis & Design, Hosting -- we do it all!
Copyright 2005 Robert Melton
Send questions and comments to
Last updated March 10th, 2005