When I edit a file that I do not own on the remote system, but I do have write permission (group or world), the save operation cannot complete.

This is due to to the rmate script creating a temporary file and then trying to chown the file with the user:group of the original file. Since I do not own the file, this fails and the write operation aborts.

Just realised it was the subject of another issue.

I tested this with both remote-atom and vscode-remote for consistency, but in both cases, when I call rmate from the command line on my debian server, the command line just hangs and no window opens on my machine. After hitting ctrl-C on my command window, rmate exits, but still no window. I checked that my ssh tunnel is working, and that there aren't write issues via executing rmate with sudo. Not sure what this could be, seeing as rmate was working a few hours ago with the same configuration.

gem install rmate
ERROR: Error installing rmate:
invalid gem: package metadata is missing in /usr/local/lib/ruby/gems/2.2.0/cache/rmate-1.5.7.gem

ruby -v
ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]

I appreciate any suggestions to force... hopefully resolved soon!

It would be useful to be able to do some form of ping protocol with rmate, just to check that the connection.
Something like rmate --ping would return 0 if everything is OK some error status if not.

I would like to use Textmate to edit content in a hierarchical CMS.

The problem is that the data is stored in an object-database, or in PostgreSQL rather than in a file system. We need to fetch the content, or write the content using https. Not access files using ssh. Fetch the contents of an object, write the contents, fetch the contents of a collection, move an object or collection and delete an object or collection. These are Python object in the database, with a name, some content, change time, file size, permissions, and content type. These objects are accessed with a path. Very much like a file system.

I suspect that a few small changes to rmate would accomplish what I want.

I could do this with the Python version of mate, but it is a bit out of date. The bash version is not so good at asynchronous operations. Ruby’s concurrency models look great.

Webdav is the other solution, but I think that rmate is much closer to what I want. For one thing Textmate already supports rmate. Just run CMSmate on the local machine and access the content over the web.

Has anyone else done something like this?
Warm Regards
Christopher Lozinski

Can you push the newest version of the gem (1.5.6) to Rubygems please?

Hello,

I tried to use rmate today on one of my servers, I installed using the gem command (gem install rmate) and it installed without errors, but when I tried to open an file, I got the following error:

adler@adler:~$ rmate .bash_history 
adler@adler:~$ setsockopt TCP_NODELAY: Invalid argument
connect_to localhost port 52698: failed.
/var/lib/gems/1.9.1/gems/rmate-1.5.7/bin/rmate:158:in `readline': end of file reached (EOFError)
    from /var/lib/gems/1.9.1/gems/rmate-1.5.7/bin/rmate:158:in `connect_and_handle_cmds'
    from /var/lib/gems/1.9.1/gems/rmate-1.5.7/bin/rmate:207:in `block in <top (required)>'
    from /var/lib/gems/1.9.1/gems/rmate-1.5.7/bin/rmate:206:in `fork'
    from /var/lib/gems/1.9.1/gems/rmate-1.5.7/bin/rmate:206:in `<top (required)>'
    from /usr/local/bin/rmate:23:in `load'
    from /usr/local/bin/rmate:23:in `<main>'

Sometimes when editing with rmate, I find that the connection closes and it takes me a while to realise what I have saved is not really being saved.

Is there the ability for some kind of alert to tell you the ssh conection has dropped, mind you this will have to be done locally as a rmate or rsub plugin. Correct?

CMD+R typically runs a script (python, bash, etc...)

Any chance rmate could allow remote execution (and print of remote log in current window) on top of remote editing?

I realize this might be hard to implement, or maybe slow on large folder?

but being able to open a folder like I am able to with mate would be so awesome.

machine$ rmate .
/usr/local/rvm/gems/ruby-2.0.0-p247/gems/rmate-1.5.5/bin/rmate:85:in `read': Is a directory - . (Errno::EISDIR)
    from /usr/local/rvm/gems/ruby-2.0.0-p247/gems/rmate-1.5.5/bin/rmate:85:in `block in read_file'
    from /usr/local/rvm/gems/ruby-2.0.0-p247/gems/rmate-1.5.5/bin/rmate:85:in `open'
    from /usr/local/rvm/gems/ruby-2.0.0-p247/gems/rmate-1.5.5/bin/rmate:85:in `read_file'
    from /usr/local/rvm/gems/ruby-2.0.0-p247/gems/rmate-1.5.5/bin/rmate:179:in `block in <top (required)>'
    from /usr/local/rvm/gems/ruby-2.0.0-p247/gems/rmate-1.5.5/bin/rmate:166:in `each_index'
    from /usr/local/rvm/gems/ruby-2.0.0-p247/gems/rmate-1.5.5/bin/rmate:166:in `<top (required)>'
    from /usr/local/rvm/gems/ruby-2.0.0-p247/bin/rmate:23:in `load'
    from /usr/local/rvm/gems/ruby-2.0.0-p247/bin/rmate:23:in `<main>'
    from /usr/local/rvm/gems/ruby-2.0.0-p247/bin/ruby_noexec_wrapper:14:in `eval'
    from /usr/local/rvm/gems/ruby-2.0.0-p247/bin/ruby_noexec_wrapper:14:in `<main>'
machine$

until directories are supported, this stacktrace should be hidden, IMO

If the user has permission to edit the file, but not to create new files in the same to the directory, saving fails silently (unless verbose is used).

$ ls -la 
total 0
drwxr-xr-x   3 root        wheel  102 Jan  3 09:22 .
drwxrwxrwt  19 root        wheel  646 Jan  3 09:22 ..
-rw-r--r--   1 sampleuser  wheel    0 Jan  3 09:22 test_file.txt

Open the file for editing:

$ rmate --host samplehost --wait test_file.txt

Make some changes, and save the file, close the tab, and the file is still empty:

$ cat test_file.txt

Repeat the above with --verbose:

$ rmate --host samplehost --wait --verbose test_file.txt 
Using TCP socket to connect: ‘samplehost:52698’
Connect: ‘220 samplehost RMATE TextMate (Darwin 15.6.0)’
Saving test_file.txt
Save failed! Permission denied - test_file.txt~
Closed test_file.txt
Done

rmate does not work if you are using an ssh socks proxy.

This works just fine:
ssh -R 52698:127.0.0.1:52698 [email protected]

But if you have to use the -D option to connect via a socks proxy, it does not work.

I tried the following and rmate does not open the file:
ssh -DR 52698:127.0.0.1:52698 [email protected]
ssh -D 52698 -R 52698:127.0.0.1:52698 [email protected]
ssh -D 55555 -R 52698:127.0.0.1:52698 [email protected]

The official ruby version: https://github.com/textmate/rmate
A bash version: https://github.com/aurora/rmate
A perl version: https://github.com/davidolrik/rmate-perl
A python version: https://github.com/sclukey/rmate-python
A nim version: https://github.com/aurora/rmate-nim
A C version: https://github.com/hanklords/rmate.c
A node.js version: https://github.com/jrnewell/jmate

copied from: https://atom.io/packages/remote-atom

it willbe usefull if you add this info to the Readme file.

Trying to close multiple files at the end of a coding session (cmd-w repeatedly in textmate) will close the first file then the terminal controlling it because on close the terminal gets focus. I'm not sure why this is the default behavior but luckily it's rather easy to fix (cmd['re-activate'] = false in line 175)

Hey thankss for your work ..!!!

I maked a proposal for corporate image you can see here ..
https://steemit.com/utopian-io/@orelmely/proposal-logo-to-textmate-open-source-editor

Blessings!!
https://steemit.com/utopian-io/@orelmely/proposal-logo-to-textmate-open-source-editor

We set it up so one PC would use 52698 and the other 52699, however this did not work and we realised that rmate only allows a single connection.

When we were on the same port, when I called rmate on my machine it popped up on the other machine.

Is there no way for multiple simultaneous connection?

when I input the following command
mbp ~/ ∑ rmate test.txt

the below terminal output is generated

connect_to localhost port 52698: failed.
mbp ~/ ∑ /Library/Ruby/Gems/1.8/gems/rmate-1.5.5/bin/rmate:149:in readline': end of file reached (EOFError) from /Library/Ruby/Gems/1.8/gems/rmate-1.5.5/bin/rmate:149:inconnect_and_handle_cmds'
from /Library/Ruby/Gems/1.8/gems/rmate-1.5.5/bin/rmate:186
from /Library/Ruby/Gems/1.8/gems/rmate-1.5.5/bin/rmate:185:in fork' from /Library/Ruby/Gems/1.8/gems/rmate-1.5.5/bin/rmate:185 from /usr/bin/rmate:19:inload'
from /usr/bin/rmate:19

I installed rmate via 'sudo gem install rmate'

thanks :)

Fresh install of rmate. Tried rmate -v for version but only got an error like this ;)

ubuntu@server:~$ rmate
connect_to 0.0.0.0 port 52698: failed.
ubuntu@server:~$ /home/ubuntu/.rbenv/versions/1.9.3-p362/lib/ruby/gems/1.9.1/gems/rmate-1.5.4/bin/rmate:149:in `readline': end of file reached (EOFError)
    from /home/ubuntu/.rbenv/versions/1.9.3-p362/lib/ruby/gems/1.9.1/gems/rmate-1.5.4/bin/rmate:149:in `connect_and_handle_cmds'
    from /home/ubuntu/.rbenv/versions/1.9.3-p362/lib/ruby/gems/1.9.1/gems/rmate-1.5.4/bin/rmate:186:in `block in <top (required)>'
    from /home/ubuntu/.rbenv/versions/1.9.3-p362/lib/ruby/gems/1.9.1/gems/rmate-1.5.4/bin/rmate:185:in `fork'
    from /home/ubuntu/.rbenv/versions/1.9.3-p362/lib/ruby/gems/1.9.1/gems/rmate-1.5.4/bin/rmate:185:in `<top (required)>'
    from /home/ubuntu/.rbenv/versions/1.9.3-p362/bin/rmate:23:in `load'
    from /home/ubuntu/.rbenv/versions/1.9.3-p362/bin/rmate:23:in `<main>'

rmate used to work on all my server for years without any issues, now recently after having to upgrade to Ruby 2.5.0 and the rubygems system, rmate stopped working with the following error message:

connect_to localhost: unknown host (nodename nor servname provided, or not known)
Traceback (most recent call last):
	6: from /root/.gem/ruby/2.5.0/bin/rmate:23:in `<main>'
	5: from /root/.gem/ruby/2.5.0/bin/rmate:23:in `load'
	4: from /root/.gem/ruby/2.5.0/gems/rmate-1.5.9/bin/rmate:222:in `<top (required)>'
	3: from /root/.gem/ruby/2.5.0/gems/rmate-1.5.9/bin/rmate:222:in `fork'
	2: from /root/.gem/ruby/2.5.0/gems/rmate-1.5.9/bin/rmate:223:in `block in <top (required)>'
	1: from /root/.gem/ruby/2.5.0/gems/rmate-1.5.9/bin/rmate:174:in `connect_and_handle_cmds'
/root/.gem/ruby/2.5.0/gems/rmate-1.5.9/bin/rmate:174:in `readline': end of file reached (EOFError)

Looking at the error message it seems like localhost couldn't resolve, but changing to 127.0.0.1 didn't help and it's widespread for me over all my server.

If multiple users are logged in on the same server forwarding the same port, files opened via rmate get sent to the user who logged in first.

I've been experiencing a very similar problem. Thank you for your post with the --wait and --verbose options! My files were just disappearing, and I couldn't figure out why!

$ls -l
-rwxrwxr-x 1 bfletcher bfletcher     0 Aug 22 11:20 temp_file.py

Error with $rmate --view --wait temp_file.py:

touch: cannot touch ‘/tmp/rmate.11068.90017’: Permission denied
/usr/local/bin/rmate: line 362: /tmp/rmate.11068.90017: Permission denied
Saving temp_file.py
cat: /tmp/rmate.11068.90017: No such file or directory
rm: cannot remove ‘/tmp/rmate.11068.90017’: No such file or directory

Originally posted by @squishbug in #53 (comment)

I'm curious as to what determines the hostname:filename to work on some systems verses others.
I've tried to take a system that it doesn't work on and upgrade to 1.9.3 and it still doesn't seem to work is this something I need to change on remote host?

Hey all!

I've been a big fan of rmate/rsub so far but just recently it's stopped working. I've checked and double-checked that everything sever-side is working, and it seems that on my local machine things aren't right.

Doing "telnet 127.0.0.1 52698" fails... I'm wondering where things went wrong, and what I can do to fix them?

Any help would be appreciated! Thanks!
-Steve

Hi
I use rmate to edit my files in the Linux server. I'm able to successfully open the files but for reason the python code is not aligned properly. Few lines are not aligned properly.

Here is a thread about this issue. Not sure what needs to be changed in sublime to make it work correctly.

https://askubuntu.com/questions/959866/files-improperly-aligned-after-transfer-via-ftp?noredirect=1#comment1533479_959866

Improves interchangeability with local "mate" command.

I tried running rmate with auto set for the host, but it didn't work due to me being connected via IPv6.

rmate-1.5.5/bin/rmate:148:in `initialize': Connection refused - connect(2) (Errno::ECONNREFUSED)

When I do an nmap scan of my IP address, it returns:
Host is up (0.0050s latency).
PORT STATE SERVICE
52698/tcp closed unknown

This likely means textmate isn't listening on IPv6. So maybe this is a report which should be under textmate and not the rmate command. Just thought I'll post here since it's with rmate.

When a file is opened in TextMate via rmate and saving fails due to the network connection being lost or rmate not having enough permissions, it still looks like TextMate saves the file perfectly.

It could be great if there was a warning when it doesn't succeed. It could lead to data loss if one closes a file with changes that has only seemingly been committed to disk.

Using TextMate 2.0-beta.7.9 and rmate version 1.5.8.

I have been trying to setup Sublime Text 3 on my local Windows 10 machine to work remotely on files on my Ubuntu 16.04 LTE server (google cloud compute engine instance). I followed these instructions: https://github.com/henrikpersson/rsub and https://github.com/textmate/rmate

I have decided to use a standalone bash version (though I apparently still needed to install ruby environment).

I have setup my rmate script in /bin/ catalogue, but when I try to run the command rmate, I get the following end of a line error:

/bin/rmate:145:in `readline': end of file reached (EOFError)
    from /bin/rmate:145:in `handle_cmd'
    from /bin/rmate:180:in `connect_and_handle_cmds'
    from /bin/rmate:223:in `block in <main>'
    from /bin/rmate:222:in `fork'
    from /bin/rmate:222:in `<main>'

I have tried simply reinstalling the script from the link provided, but it didn't help. I also made sure that the rest of my installation: config file on my local machine and my firewall rules and sshd config files are correct.

I would be grateful if you pointed me in the directoin of what I am missing.

I run it on Freebsd 9.1. It is working, but always print out warnings like:

/usr/local/lib/ruby/site_ruby/1.9/date.rb:196: warning: assigned but unused variable - m
/usr/local/lib/ruby/site_ruby/1.9/date.rb:212: warning: assigned but unused variable - d
/usr/local/lib/ruby/site_ruby/1.9/date.rb:286: warning: assigned but unused variable - nd
/usr/local/lib/ruby/site_ruby/1.9/date.rb:301: warning: assigned but unused variable - nd
/usr/local/lib/ruby/site_ruby/1.9/date.rb:301: warning: assigned but unused variable - nf
/usr/local/lib/ruby/site_ruby/1.9/date.rb:318: warning: assigned but unused variable - nk
/usr/local/lib/ruby/site_ruby/1.9/date/format.rb:561: warning: character class has duplicated range: /\A[\s\v]/
/usr/local/lib/ruby/site_ruby/1.9/date/format.rb:562: warning: character class has duplicated range: /\A[\s\v]+/
lib/rational.rb is deprecated

I don't know ruby. Any thoughts to remove them?

Using ssh -R 52698:127.0.0.1:52698 server cause the following error

rmate .bash_profile
connect_to 127.0.0.1 port 52698: failed.
 /home/bin/rmate:154:in `readline': end of file reached (EOFError)
    from /home/bin/rmate:154:in `connect_and_handle_cmds'
    from /home/bin/rmate:191
    from /home/bin/rmate:190:in `fork'
    from /home/bin/rmate:190

when it worked in the previous stable release

Hi,

I got the following error when logging back to my ssh server after I got a broken pipe ssh connection (probably due to time out). The username is my username on the cluster I logged into.

Warning: remote port forwarding failed for listen port 52698

Then when I use rmate to open a file, it gives:

/home/username/bin/rmate:174:in `readline': end of file reached (EOFError)
    from /home/username/bin/rmate:174:in `connect_and_handle_cmds'
    from /home/username/bin/rmate:223
    from /home/username/bin/rmate:222:in `fork'
    from /home/username/bin/rmate:222

netstat -ltnp | grep 52698 gives the following:

(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 127.0.0.1:52698             0.0.0.0:*                   LISTEN      -                   
tcp        0      0 ::1:52698                   :::*                        LISTEN      -   

It seems that I cannot see the pid of those connections. I am just wondering if there's any way to close those dead connections so that I can use rmate again.

I know that logging out completely and waiting for a while will get those connections wiped out on the cluster. But I just wonder if there's a more efficient way to addressing the problem.

I have been using remote editing with textmate by ssh tunnel method for a while. (Thanks to it, I was able to resume my work anywhere with internet access.)

gem update rmate does not update version to 1.5.6 as it is not available on rubygems.org is this intended?

https://github.com/davidolrik/rmate-perl

It is related to reading from stdin, (i..e, echo foo | rmate -). What I notice is that when I save the file in the pop up window, a file called "-" is saved in the remote server.

Possible solution: the file should not be saved if the token is "-".

I am having an odd issue wherein suddenly port forwarding stopped working in a particular scenario for me. By default I have ssh set to use the following config (my ~/.ssh/config file):

Host *
    ControlMaster auto
    ControlPath /tmp/%r@%h:%p
    ServerAliveInterval 120
    ServerAliveCountMax 3

    ForwardX11 yes
    ForwardX11Trusted yes

    RemoteForward 52698 127.0.0.1:52698

I then initiate ssh to the server (ssh [email protected]) and query my local workstation to make sure that there are listeners for port 52698; sudo lsof -i -P | grep 52698:

AppName   40262        username   45u  IPv6 0x4b497d2de68055a1      0t0    TCP *:52698 (LISTEN)
sshd      92207        username   14u  IPv6 0x4b497d2d9e7ec4a1      0t0    TCP localhost:52698 (LISTEN)
sshd      92207        username   15u  IPv4 0x4b497d2dbb985641      0t0    TCP localhost:52698 (LISTEN)

I then likewise make sure that the port is active on the server, lsof -P | grep 52698:

sshd      16366      root    7u     IPv6             196798        0t0        TCP localhost:52698 (LISTEN)
sshd      16366      root    8u     IPv4             196799        0t0        TCP localhost:52698 (LISTEN)

I simply get hangs or effective timeouts right now when I initiate rmate.sh on the server to which I'm logged into in each case. With the rb version of rmate I'm getting the following error which leads me to believe that something is wrong with the tunnel now:

[~]# /usr/local/rvm/gems/ruby-1.9.3-p448@global/gems/rmate-1.5.5/bin/rmate:149:in `readline': end of file reached (EOFError)
    from /usr/local/rvm/gems/ruby-1.9.3-p448@global/gems/rmate-1.5.5/bin/rmate:149:in `connect_and_handle_cmds'
    from /usr/local/rvm/gems/ruby-1.9.3-p448@global/gems/rmate-1.5.5/bin/rmate:186:in `block in <top (required)>'
    from /usr/local/rvm/gems/ruby-1.9.3-p448@global/gems/rmate-1.5.5/bin/rmate:185:in `fork'
    from /usr/local/rvm/gems/ruby-1.9.3-p448@global/gems/rmate-1.5.5/bin/rmate:185:in `<top (required)>'
    from /usr/local/rvm/gems/ruby-1.9.3-p448@global/bin/rmate:19:in `load'
    from /usr/local/rvm/gems/ruby-1.9.3-p448@global/bin/rmate:19:in `<main>'
    from /usr/local/rvm/gems/ruby-1.9.3-p448@global/bin/ruby_noexec_wrapper:14:in `eval'
    from /usr/local/rvm/gems/ruby-1.9.3-p448@global/bin/ruby_noexec_wrapper:14:in `<main>'

I also did set /etc/rmate.rc to this for good measure:

port: 52698

Any ideas here as to what may be going on or any way to coax rmate.rb to offer some more insight on the connectivity issue?

I couldn't get the directions here working, and figured I must have misunderstood something, so I tried the directions here: http://hiltmon.com/blog/2013/11/09/textmate-2-basics/

That didn't work either, so it appears that the problem is with rmate.

After attempting to rmate .bash_profile from ~ on the VM, I just get a new prompt, and after a little while of waiting I get:

$ /usr/local/bin/rmate:174:in `initialize': Connection timed out - connect(2) (Errno::ETIMEDOUT)
    from /usr/local/bin/rmate:174:in `new'
    from /usr/local/bin/rmate:174:in `connect_and_handle_cmds'
    from /usr/local/bin/rmate:228:in `block in <main>'
    from /usr/local/bin/rmate:227:in `fork'
    from /usr/local/bin/rmate:227:in `<main>'

Here is my .ssh/config for the Vagrant VM. All normal vagrant commands work, so I'm quite sure everything is good in that regard, but using the rmate command from inside the Vagrant VM fails.

Host ads
  HostName 127.0.0.1
  User vagrant
  Port 2222
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no
  PasswordAuthentication no
  IdentityFile /Users/brandon/Code/ad-related-reports/.vagrant/machines/default/virtualbox/private_key
  IdentitiesOnly yes
  LogLevel FATAL

  RemoteForward 52698 127.0.0.1:52698

TextMate does have permission to allow incoming connections in the Firewall settings. I even tried turning off the firewall, but that made no difference.

Using rmate with an ssh remote tunnel:
RemoteForward 52698 127.0.0.1:52698
crashes:

$ ~/bin/rmate --version
rmate version 1.5.6 (2013-08-02)
$ ~/bin/rmate tmp/file.log
connect_to 127.0.0.1 port 52698: failed.
~/bin/rmate:153:in `readline': end of file reached (EOFError)
    from ~/bin/rmate:153:in `connect_and_handle_cmds'
    from ~/bin/rmate:192
    from ~/bin/rmate:191:in `fork'
    from ~/bin/rmate:191

(paths edited)

Workaround: use
RemoteForward 52698 localhost:52698

Tested with RedHat 6 and Ubuntu 13.04

It would be very useful if
rmate /some/dir
worked the same as it does locally.

For saving a huge amount of time to someone, please make a correction in the following things:

1. in blog post http://blog.macromates.com/2011/mate-and-rmate/ you say that we should use 127.0.0.1. No, it needs to be localhost.
2. with host: auto in /etc/rmate.rc it doesn't work, but with host: 127.0.0.1 it works.
3. TM should be open locally if you want to user rmate.

Thanks.
//EDIT Removed part about ruby20 -- it works with ruby20 as well (it was a gem issue) and added 3.

Hi, I'm trying to use rmate but consistently get the above error. The command I use to ssh is : ssh -R 52698:localhost:52698 ...
I had rmate working for a few years but then at some point last year this started happening every time. I don't know if it's due to a new version of Mac OS locally, or perhaps a new version of linux on the server. I have Max OS Montery v12.6.3 locally and CentOS 7 (Core) on the server. rmate is installed on the server at $HOME/.gem/ruby/gems/rmate-1.5.9/bin/rmate.

I'd like to be able to rmate *.rb in a directory. Currently it reports:
There is more than one file specified. Opening only ... and ignoring other.

However, I can rmate a.rb and then rmate b.rb etc. successfully. Would be nice to allow this directly from the script.