Yo Greg I've never done this before either, but after another minute of squinting at the manpage I tried this:
$ screen -X at 4 stuff asdf and it seems to work fine. I.e. asdf shows up on the commandline of window number 4. Do read the manpage. The whole manpage. Closely. There's probably a better way that I missed. E.g. the 'process' command looks promising. 2008/6/12 Greg Novak <[EMAIL PROTECTED]>: > Thanks for the info. However, I can't get it to work for me. I've > tried things like: > > screen -X "stuff command" > screen -X "stuff command\n" > screen -r -X "stuff command\n" > screen -r -X 'stuff "command\n"' > > and permutations of the above variations. Did I fail to understand > what you meant? > > Sorry to be dense about this, > Greg > > 2008/6/10 Jean Jordaan <[EMAIL PROTECTED]>: >> Hi Greg >> >>> I realize that screen expects to have an interactive user at one end >>> of its connection, and therefore I'm in some sense misusing the >>> program. >> >> Well, not if you use 'screen -X'. Maybe the 'stuff' command helps: >> >> stuff string >> >> Stuff the string string in the input buffer of the current window. >> This is like the "paste" command but with much less overhead. You can‐ >> not paste large buffers with the "stuff" command. It is most useful for >> key bindings. See also "bindkey". >> >> -- >> jean . .. .... //\\\oo///\\ >> >> >> _______________________________________________ >> screen-users mailing list >> screen-users@gnu.org >> http://lists.gnu.org/mailman/listinfo/screen-users >> > -- jean . .. .... //\\\oo///\\ _______________________________________________ screen-users mailing list screen-users@gnu.org http://lists.gnu.org/mailman/listinfo/screen-users
