-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emacs support? #125
Comments
Hi @tomjridge , thanks for your interest in Tandem! However, if you are interested in developing a Tandem plugin for Emacs, we'd be delighted to help out along the way and more than welcome Pull Requests. |
@rageandqq could you clarify what the Tandem agent is exactly? i see that the neovim plugin requires the |
The |
@anarcat The Tandem agent implements all of the common functionality that all plugins need (e.g. managing peers in a session, sending messages between peers, etc.). We actually use the CRDT that powers Teletype under the hood. Since they implemented it in JavaScript, we need to take on the Node.js dependency in order to actually use it with the agent. |
I've got something work-in-progress here https://github.com/jscheid/tandem-emacs It works pretty well when joining a session, hosting a session (and joining it with Sublime) seems broken in the agent? |
@jscheid i've run into the same issue when trying to host via the command line and join via sublime. Looking at the log all I get are the following messages:
|
oh boy, how exciting! didn't expect that to happen so soon :) congrats on the author and keep it up! should we report issues there or here? (this only makes licensing issues described in #131 even more pressing unfortuantly...) |
@anarcat since we are not modifying their agent, and it is their agent that is communicating with the server it might be ok. Alternatively we can point it to another server. |
On 2018-03-15 14:50:45, Alexander Griffith wrote:
@anarcat since we are not modifying their agent, and it is their agent that is communicating with the server it might be ok. Alternatively we can point it to another server.
Well, the license on the emacs plugin itself is not a concern here. The
concern is the license of the agent. You still have to use agent to
operate the plugin, and so agree to its license. Changing the server
doesn't resolve the fundamental non-freeness of the license... But I
disgress, this is a discussion for the other issue. :)
|
the license will change, so nevermind those comments :) whoohoo! |
@anarcat @alexjgriffith The license has been updated! See #135. Hope this quells your concerns 😄 @jscheid That's awesome! I too didn't expect this to happen so soon. What version of |
I have Python 3.6.4 from homebrew. Could it be a discrepancy between the version of the agent used by the Sublime plugin and the one I'm using? |
Does it work with the vim plugin? I have tried using the same agent for both the Emacs extension and Sublime plugin and still could not host on Emacs. |
It turns out Emacs hasn't quite achieved sentience yet and didn't know to send the initial buffer when hosting a session without me telling it to... it should work better now. |
By the way, what are the criteria for getting it listed as the (or as "an") unofficial Emacs plugin in the README and on the home page? |
What's the status here? It seems that the plugin haven't changed since march, does it actually work? Should Emacs be included in the list of supported clients? |
No description provided.
The text was updated successfully, but these errors were encountered: