savergugl.blogg.se - Iterm copy to clipboard

It’s a tiny bit of obscure setup but having it a single keystroke away and the convenience of the other things I can do mean that it pays dividends, even if I’ve only … twice? seen something truly hinky in the results.

similarly, if you remote in from several different local computers to the same remote machine using the same remote port (e.g.Good advice last time this advice came up on Lobste.rs, my approach got voted down, but it’s realistic and honest: if I’m going to paste anything from an untrusted source near a command interpreter, I hit alt-v (or esc-v) to invoke a text editor (edit-command-line widget in zsh, bound in my shell) and then "+p to paste from the clipboard/selection into the text editor, where I can look at it, make sure I haven’t mis-selected text, that nothing else was happening adjust as appropriate, and then save, which drops the edited line back in the shell line-editor, waiting for me to hit return.

if you initiate more than one SSH session with the same remote port forwarding to the same remote machine, only the first one will have any effect no "duplicate port" type errors will be reported on either end.

You can even dynamically decide whether or not to send any data, based on whether or not anyone is listening (there's probably a more efficient way to do this, but it works): #!/bin/bashĬnt=`(netstat -lnptu 2>/dev/null) | grep 127.0.0.1:9999 | grep -v grep | wc -l` You can get as complicated as you'd like: $ nc localhost 9997 `ls -ld *` On the remote end I use netcat to send the desired content back to the listening daemon. See the config file man page link below for more options. With that, any time that I SSH to a host whose name starts with 'ufo', the remote forwarding from 9997 to localhost:9999 will automatically be set up. Here's an example from my ~/.ssh/config file: Host ufo* If you don't feel like typing the -R 9997:localhost:9999 on every SSH invocation you make, you can put the remote forwarding definition in the SSH config file to do it automatically. You can remote into the same remote machine multiple times with the same command, and it will sort of work as expected see note below. To setup this tunnel, execute the following command: $ ssh -R 9997:localhost:9999 can remote into multiple different remote machines with the same command and all will function as expected. I could use port 9999 on both the remote machine and the local computer, but I don't need to.

Specifically, I create a link from the remote machines's port 9997 to the local computer's port 9999, which now has a daemon listening on it, thanks to the launchd stuff above. To make this as painless and dynamic as possible, I've used SSH port-forwarding to create a dynamic link from the remote machine back to the local computer (the how's and why's of this are beyond this answer see below for more information). SSH Port-Forwardingīecause I could be accessing the remote machine from several different local computers, I can't hard-code the sending of the data on the remote machine to a specific host. Note: you will need to set this up on each local host you want this to work on. If you would like this to load every time you login, place the plist file into the ~/Library/LaunchAgents directory. You can see that it's loaded or remove it with the following commands: $ launchctl list local.pbcopy.9999 In order to load the daemon, run the following command: $ launchctl load Once you have things working, you can remove the StandardOutPath and StandardErrorPath keys and strings, as they're only needed for debugging. If you wish to use a port other than 9999, just change it everywhere (keeping in mind that it should be something above 1024 and should not be a well-known port that you might already be using). In Terminal.app that doesnt happen, so I suppose thats a very specific bug and annoying bug (because I end up pasting undesirable text). When I select some text and press 'Cmd + c', it merges the text into the clipboard - but it should only merge when double tapping 'c'. plist appended, so for the above example, it would be . I am experiencing a bug when copying text in iTerm 2.

Mine looked like this: īy convention, the plist file name should be the label name with. To do this you need to setup a launchd plist file. The daemon process will simply call pbcopy, which will take anything passed in via STDIN and put it on the clipboard.

Local Daemonįrom the local computer (OSX), setup a daemon to listen on a specific port, via launchd (see links below). Piecing together lots of information from several different sources, here's what I came up with.