You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
durr@testcnc:~$ rmate /usr/lib/tcltk/linuxcnc/bin/halshow.tcl
File /usr/lib/tcltk/linuxcnc/bin/halshow.tcl is not writable! Use -f to open anyway.
durr@testcnc:~$ rmate /usr/lib/tcltk/linuxcnc/bin/halshow.tcl -f
File /usr/lib/tcltk/linuxcnc/bin/halshow.tcl is not writable! Use -f to open anyway.
durr@testcnc:~$ rmate -f /usr/lib/tcltk/linuxcnc/bin/halshow.tcl
< file opens >
For shell commands, I generally assume that flags can go anywhere. However, rmate seems to only parse arguments rmate <here> filename.
This is, well, certainly unexpected, if not a huge issue. It'd be nice if arguments to rmate behaved like every other well-behaved command-line tool.
The text was updated successfully, but these errors were encountered:
For shell commands, I generally assume that flags can go anywhere. However, rmate seems to only parse arguments
rmate <here> filename
.This is, well, certainly unexpected, if not a huge issue. It'd be nice if arguments to
rmate
behaved like every other well-behaved command-line tool.The text was updated successfully, but these errors were encountered: