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
It might not be shared editing for vim -- but it is shared editing on platforms besides the Mac -- which is a step in the right direction. Check it out => http://me.sphere.pl/indexen.htm
-- MetaCosm 08 Feb 2005
<small>P lesbo bondage mature lesbiche lesbo photos lesbiche in calore lesbiche troie www lesbo101
pee asian pissing golden shower bed wetting piss video clips pissing gallery boys shitting
rough xxx rude sex rude pics rude photos rude sex rough sex videos
chubby fuck plumper teens chubby boobs cubby biggercity chubby porn
cruel strapon mistress cruel cruel anime cruel site cruel site cruel drawing
xxx shop anal sex xxx young girls video xxx dragon ball z xxx homemade xxx
|?
violent rape stories violent pics violent websites violent xxx violent video violent acts
asian pee piss slave peed piss lover piss on you women peeing
</small>