The content of my ~/.bash_profile is: # Tell ls to be colourful The Terminex were fairly scientifically advanced. Here, between every line, I moved my cursor somewhere else on my Desktop. Many eons ago, an alien race known as the Terminex, had been judged unfit to live by the almighty powerful Celestials. If I click several times, then the combination of these characters will appear the same number of times.īy moving my cursor, I can change the combination of letters. When I click on the terminal window, a succession of characters appear. I come back and it's written broken pipe.
TERMIUS CHARACTER PASSWORD
See option ControlMaster in ssh_config(5) to make that faster to execute (and without password prompting).The problem I have happens after a ssh connection has been ended by closing my MacBook (putting it in stand-by mode). SSHFS does provides for some caching (see sshfs(1) options cache, cache_timeout, cache_x_timeout) to alleviate that problems somewhat.Īlso, if you want to execute something on remote you need to use another screen or prefix all commands with " ssh remotehost" (for example ssh remotehost sudo service apache restart). Also, (the best feature IMHO) you can use your local editor of choice for lag-free editing of remote files.ĭisadvantages are (especially if you link is also low-bandwidth, and not only high-latency) that for each file to be edited, it needs to be fully transfered to localhost, and then after edit, fully transfered to remote again. The advantage is not only that your shell (and its line editing) is local and lag-free, but also that you can navigate remote filesystem and use shell filename completion ( tab key) for remote files. On the unconventional side, you could alternatively use to mount remote filesystem locally. It's work in progress, though, so pull requests or workable ideas for improvement are welcome! Also, remote tab filename completion currently works only by dropping you back to char-by-char mode (or uses local filesystem instead of remote one, depending on your preferences). And (as it just wraps around your system ssh client) there is no danger of not keeping up with ssh security fixes.ĭisadvantage is you either need to press hotkey to enter local line editing mode every time you want it, or you need to modify prompt on remote host to allow autodetection. And editors and other curses-based programs continue to work normally (albeit with lag) in default char-by-char mode as in normal ssh connection. Also, nothing needs to be changed on servers or firewalls. So you could enter (with editing, command recalling etc) whole line locally, and then when you press enter it will be sent as one TCP packet to remote side.Īdvantage is lag-free command line editing (like old telnet cooked/canonical "line-by-line buffered mode", but with superior editing commands provided by GNU readline). Having had the same issue ( high latency and packet loss due to terrible mobile data quality at some locations), and mosh not cutting it for me (it needs special programs on all remote hosts, fixing UTF8 locally and remotely on all servers without breaking them, modifying all the firewalls - and it doesn't really provide local line editing anyway) I've decided to write a small wrapper to provide local line editing mode for ssh.īy default, it just passes everything to ssh in default char-by-char mode, but you can press a hotkey to enter readline-powered local line editing mode at any time.
0 kommentar(er)
