Sorry, left out something. After putting the commands into the register, then
use "process" with that register:
register r "^A:eval 'echo text one' 'sleep 3' 'echo text 2'^M"
process r
___
screen-users mailing list
screen-users@gnu.org
http://lists.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
clemens fischer wrote:
> On Thu-2009/04/30-16:47 clemens fischer wrote:
>
>> Recently I needed a screen command sequence more complex than the
>> usual key "bind" or "stuff". I turned to "process [key]", as the man
>> page said: "command can be used
On Monday 15 June 2009 17:02:23 clemens fischer wrote:
> Would it be true to say that "process" is like "stuff", but it handles
> text in registers instead of literal text?
Yes, but "process" handles the text "as if it had been typed in from the
user’s keyboard." Keep that in mind.
> say I have:
On Thu-2009/04/30-16:47 clemens fischer wrote:
> Recently I needed a screen command sequence more complex than the
> usual key "bind" or "stuff". I turned to "process [key]", as the man
> page said: "command can be used to bind multiple actions to a single
> key".
Would it be true to say that "p
Hi,
I've written a program called eventlogger.c[1] based on the newer posix
message queues[2]. It simply sets up a queue[3] and lets you place one
line of text into it. In the other mode, without giving it text, it
will read out what's in the queue, highest priority messages first.
I use it to
