Re: Question collaborative editing.

[Pankaj Jangid]

On Fri, Oct 02 2020, Michael Albinus wrote:

>>>An example use-case might be:
>>>
>>>user1:
>>>1. C-x C-f (find-file)
>>>2. M-x enable-collaboration ; this generates a session-key
>>>3. Share session key with collaborators via chat/email
>>>
>>>user2: (via Tramp)
>>>1. C-x C-f /collab:session-key@ip-address:filename <RET>
>>>
>>>Users get cursors with different colours.
>>>
>>>The advantage of using Tramp is that users can always use Ad-hoc
>>>multi-hops.
>>>
>> Yes, this is exactly my expected workflow more or less. It is p2p as I
>> have mentioned before I would prefer it to be. The tramp integration is
>> something way far from my capabilities, but in general that's the
>> idea ;).
>
> I don't want to be the grinch, but pls remember what Tramp is: a library
> for alternative implementations of file operations. I don't see yet how
> /collab:session-key@ip-address:filename fits into the game, but maybe it
> needs more details to understand. For example, which file operations
> shall be treated.
>
> Furthermore, I also don't understand what needs to be done on the remote
> side wrt collaboration. A remote file in Emacs is still a file,
> connected to a buffer. All primitive file operations can be applied on
> this.

Tramp example was basically to consider the point that people are
already familier with the syntax to open a remote file (format -
/protocol:identification:resource). *We can propose and use any other
familier format*.

Secondly, I was not thinking about the implementation. I was thinking
from a user's perspective. I was thinking of these two properties - (1)
Attaches a remote file with a buffer (2) If the user is using automatic
desktop-save and desktop-read, then tramp buffers are not reconnected.