textmate/rmate

Crazy output when no arg provided

Closed this issue · 5 comments

parkr commented

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>'
sorbits commented

Calling rmate -v is verbose. Use --version (or --help).

It errors trying to connect to host 0.0.0.0. There are a few ways to specify host, the default should be localhost.

Try call it with --host to override potential config, and of course provide a host it can connect to (i.e. a way to reach your local mac).

parkr commented

Good to know. So specifying no argument shouldn't show --help or something? It's a valid call?

sorbits commented

It mimics the “real” mate (which brings TextMate to front with no
arguments) as initially, there was just this one script (rmate works
locally as well).

But it should probably be changed.

On 16 Mar 2013, at 16:58, Parker Moore wrote:

Good to know. So specifying no argument shouldn't show --help or
something? It's a valid call?

Reply to this email directly or view it on GitHub:
#13 (comment)

AJ-Acevedo commented

Just an FYI. rmate did not initially work on my Debian 6 server. I received the same error. Not until I ran rmate without any arguments did it start working as expected.

mjobin-mdsol commented

worked as expected here..

machine$ rmate
machine$

no output.

the error you get is normal if you haven't setup the ssh tunnel.

maybe the ruby stacktrace could be removed from the output when that happen though.