-
Notifications
You must be signed in to change notification settings - Fork 124
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
Does not support the +N syntax and cannot be used as $EDITOR #47
Comments
I think this should be easy to implement. I'll have a look at it, thanks for your suggestion. |
Could you have a look at my latest commit? I think it should work now what you would like to do. |
The latest commit seems to be working but the caret stays on line 1. Same issue with rmate --line 3 /tmp/x |
mmm ... i have to admit that i only tested with textmate ... i'll have a look at sublime later today. |
It does not seem to be possible with sublime text. at least: the subl command of sublime text itself does not offer a |
The syntax is FILE:LINE_NUMBER, example:
|
Apparently i misunderstood how things work with sublime text. Sublime text is using the rsub package to achieve the remote editing functionality. So in my opinion a fix for the problem would belong to this package. As i am not the author of rsub, there's not much that i can do. But i'll have a look at it and maybe i can provide a patch for it ... |
Thanks
|
@cyril-bouthors i think i have a working patch for this, as i don't know how fast the original author of rsub is, you can fetch the change from my rsub fork at https://github.com/aurora/rsub in the meantime. |
Great! On Thu, Mar 17, 2016 at 5:38 PM Harald Lapp notifications@github.com
|
rmate does not support the +N syntax which is supposed to place caret on line number after loading file, just like --line:
Others editors like vi, emacs, mg support this, even nano:
I prevents some program like 'debchange' to work:
and SublimeText opens the file called "+3"
Would it be possible to support +N as an alias to --line=N?
Thank you
PS: sorry about my initial bug report, I apparently triggered a shortcut to open the ticket before it was done
The text was updated successfully, but these errors were encountered: