randy3k / RemoteSubl

Use rmate with Sublime Text, an improved fork of rsub.
327 stars 20 forks source link

Sublime Text 3 with MacOS High Sierra #1

Closed thomson closed 6 years ago

thomson commented 6 years ago

I'm having an issue where I cannot open remote files in sublime text 3 (3143) with this package.

My .ssh/config is set with the RemoteForward 52698 localhost:52698 option.

I've installed the rsubl per your readme instruction on that remote server.

With Sublime Text 3 running, and issuing rsubl with verbose on the remote server seemingly shows that it times out.

If I open Textmate 2.0-rc4, then the rsubl remote command opens the remote file in Textmate.

On my local machine, with textmate running, doing a telnet localhost 52698 connects. With Sublime Text 3 open and Textmate closed - running telnet localhost 52698 does not connect.

randy3k commented 6 years ago

With textmate closed, could you restart sublime and check if the console has any messages related to RemoteSubl?

thomson commented 6 years ago
reloading plugin RemoteSubl.remote_subl
plugins loaded
Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 210, in on_api_ready
    m.plugin_loaded()
  File "remote_subl in /Users/jesse/Library/Application Support/Sublime Text 3/Installed Packages/RemoteSubl.sublime-package", line 313, in plugin_loaded
  File "./python3.3/socketserver.py", line 430, in __init__
  File "./python3.3/socketserver.py", line 441, in server_bind
OSError: [Errno 48] Address already in use
thomson commented 6 years ago

With the address already in use error. I restarted my machine. Upon restart and viewing the console - I did not receive the error and your package is working as intended.

Before the restart, I probably should have checked what was using 52698 with something on my local machine like sudo lsof -i -P | grep 52698 and perhaps killing the PIDs

randy3k commented 6 years ago

Would it be possible that the port was used by textmate?

thomson commented 6 years ago

I did ensure that Textmate was closed and any connections/tunnels I had open were closed. Perhaps there was some zombie process or instance of something using that port for some reason - but I didn't investigate prior to restarting.