Expect send KEY_DOWN and KEY_UP events to Process in Linux - linux
I want to simulate embedded linux keypress events to my Qt GUI Application. Primarily I want to simulate KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, and KEY_F{1-2-3} key presses. I don't have X available.
There is an ASCII character table here:
http://foldoc.org/ASCII+character+table\
And I understand how to send things, say CNTRL-T, using that table to my aplication by spawning it and sending it the following in my expect script:
send "\x14"
I can't seem to find documentation or examples on how to send the KEY_??? key presses using Expect. How can I do this using Expect?
If not possible, is there some other way to send keypresses to my process? I can't seem to be able to echo escape sequences to /dev/input/keypad...
Update:
Thanks for the comments.
I can see the output that my arrow keys generate by doing:
$ od -c
^[[D^[[C^[[D^[[B^[[A^[[A^[[B^[[B^C
I can also see the output of infocmp xterm as:
am, bce, km, mc5i, mir, msgr, npc, xenl,
colors#8, cols#80, it#8, lines#24, pairs#64,
acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
bel=^G, blink=\E[5m, bold=\E[1m, cbt=\E[Z, civis=\E[?25l,
clear=\E[H\E[2J, cnorm=\E[?12l\E[?25h, cr=^M,
csr=\E[%i%p1%d;%p2%dr, cub=\E[%p1%dD, cub1=^H,
cud=\E[%p1%dB, cud1=^J, cuf=\E[%p1%dC, cuf1=\E[C,
cup=\E[%i%p1%d;%p2%dH, cuu=\E[%p1%dA, cuu1=\E[A,
cvvis=\E[?12;25h, dch=\E[%p1%dP, dch1=\E[P, dl=\E[%p1%dM,
dl1=\E[M, ech=\E[%p1%dX, ed=\E[J, el=\E[K, el1=\E[1K,
flash=\E[?5h$<100/>\E[?5l, home=\E[H, hpa=\E[%i%p1%dG,
ht=^I, hts=\EH, ich=\E[%p1%d#, il=\E[%p1%dL, il1=\E[L,
ind=^J, indn=\E[%p1%dS, invis=\E[8m,
is2=\E[!p\E[?3;4l\E[4l\E>, kDC=\E[3;2~, kEND=\E[1;2F,
kHOM=\E[1;2H, kIC=\E[2;2~, kLFT=\E[1;2D, kNXT=\E[6;2~,
kPRV=\E[5;2~, kRIT=\E[1;2C, kb2=\EOE, kbs=\177, kcbt=\E[Z,
kcub1=\EOD, kcud1=\EOB, kcuf1=\EOC, kcuu1=\EOA,
kdch1=\E[3~, kend=\EOF, kent=\EOM, kf1=\EOP, kf10=\E[21~,
kf11=\E[23~, kf12=\E[24~, kf13=\EO2P, kf14=\EO2Q,
kf15=\EO2R, kf16=\EO2S, kf17=\E[15;2~, kf18=\E[17;2~,
kf19=\E[18;2~, kf2=\EOQ, kf20=\E[19;2~, kf21=\E[20;2~,
kf22=\E[21;2~, kf23=\E[23;2~, kf24=\E[24;2~, kf25=\EO5P,
kf26=\EO5Q, kf27=\EO5R, kf28=\EO5S, kf29=\E[15;5~,
kf3=\EOR, kf30=\E[17;5~, kf31=\E[18;5~, kf32=\E[19;5~,
kf33=\E[20;5~, kf34=\E[21;5~, kf35=\E[23;5~,
kf36=\E[24;5~, kf37=\EO6P, kf38=\EO6Q, kf39=\EO6R,
kf4=\EOS, kf40=\EO6S, kf41=\E[15;6~, kf42=\E[17;6~,
kf43=\E[18;6~, kf44=\E[19;6~, kf45=\E[20;6~,
kf46=\E[21;6~, kf47=\E[23;6~, kf48=\E[24;6~, kf49=\EO3P,
kf5=\E[15~, kf50=\EO3Q, kf51=\EO3R, kf52=\EO3S,
kf53=\E[15;3~, kf54=\E[17;3~, kf55=\E[18;3~,
kf56=\E[19;3~, kf57=\E[20;3~, kf58=\E[21;3~,
kf59=\E[23;3~, kf6=\E[17~, kf60=\E[24;3~, kf61=\EO4P,
kf62=\EO4Q, kf63=\EO4R, kf7=\E[18~, kf8=\E[19~, kf9=\E[20~,
khome=\EOH, kich1=\E[2~, kmous=\E[M, knp=\E[6~, kpp=\E[5~,
mc0=\E[i, mc4=\E[4i, mc5=\E[5i, meml=\El, memu=\Em,
op=\E[39;49m, rc=\E8, rev=\E[7m, ri=\EM, rin=\E[%p1%dT,
rmacs=\E(B, rmam=\E[?7l, rmcup=\E[?1049l, rmir=\E[4l,
rmkx=\E[?1l\E>, rmso=\E[27m, rmul=\E[24m, rs1=\Ec,
rs2=\E[!p\E[?3;4l\E[4l\E>, sc=\E7, setab=\E[4%p1%dm,
setaf=\E[3%p1%dm,
setb=\E[4%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,
setf=\E[3%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,
sgr=\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m%?%p9%t\E(0%e\E(B%;,
sgr0=\E[m\E(B, smacs=\E(0, smam=\E[?7h, smcup=\E[?1049h,
smir=\E[4h, smkx=\E[?1h\E=, smso=\E[7m, smul=\E[4m,
tbc=\E[3g, u6=\E[%i%d;%dR, u7=\E[6n, u8=\E[?1;2c, u9=\E[c,
vpa=\E[%i%p1%dd,
I've tried several of the simple escape sequences on a 'menuconfig' ( much like Linux ) program for Buildroot like so:
#!/usr/bin/expect --
# Span menuconfig
spawn make menuconfig
expect *
send {"\e[D"}
#send {"\e[%p1%dB"}
interact
I'd like to have the menuconfig open and the cursor move down one spot. However, it just launches and quits right away, even though I have an 'interact' statement in there. Any ideas as to why? Thanks -
Have you tried using autoexpect ?
Try this :
$ autoexpect
And do what you want expect to do, if you would like it to scroll two lines down - send two down arrow events - do this by pressing down arrow twice.
Then exit autoexpect with Ctrl+C
Autoexpect will generate a script of all your actions that you can then run if you want expect to repeat the same thing. What is more important is that it will also catch the key events you want to send and generate correct lines of expect script that send these events. In my case (down arrow) this was
send -- "^[OB"
Just press all the keys you want to automatically send, and then inspect the generated script (usually named script.exp).
Hope this helps
Related
Text in Bash terminal getting overwritten! Using JS, Node.js (npms are: inquirer, console.table, and mysql)
Short 10sec video of what is happening: https://drive.google.com/file/d/1YZccegry36sZIPxTawGjaQ4Sexw5zGpZ/view I have a CLI app that asks a user for a selection, then returns a response from a mysql database. The CLI app is run in node.js and prompts questions with Inquirer. However, after returning the table of information, the next prompt overwrites the table data, making it mostly unreadable. It should appear on its own lines beneath the rest of the data, not overlap. The functions that gather and return the data are asynchronous (they must be in order to loop), but I have tried it with just a short list of standard synchronous functions for testing purposes, and the same problem exists. I have tried it with and without console.table, and the prompt still overwrites the response, as a console table or object list. I have enabled checkwinsize in Bash with shopt -s checkwinsize And it still persists. Is it Bash? Is it a problem with Inquirer?
I was having this issue as well. In my .then method of my prompt I was using switch and case to determine what to console log depending on the users selection. Then at the bottom I had an if statement checking to if they selected 'Finish' if they didn't I called the prompt function again, which I named 'questionUser'. That's where I was having the issue, calling questionUser again was overriding my console logs. What I did was I wrapped the questionUser call in a setTimeout like this: if(data.option !== 'Finish'){ setTimeout(() => { questionUser(); }, 1000); } This worked for me and allowed my console log data to not get deleted. Hopefully if anyone else is having this issue this helps, I couldn't find an answer to this specific question anywhere.
Communication with Python and Supercollider through OSC
I'm trying to connect Python with Supercollider through OSC, but it's not working. I'm using Python3 and the library osc4py3. The original idea was to send a text word by word, but upon trying I realized the connection was not working. Here's the SC code: ( OSCdef.new(\texto,{ |msg, time, addr, port| [msg, time, addr,port].postIn; }, '/texto/supercollider', n ) ) OSCFunc.trace(true); o = OSCFunc(\texto); And here's the Python code: osc_startup() osc_udp_client("127.0.0.1", 57120, "supercollider") ## here goes a function called leerpalabras to separate words in rows. with open("partitura.txt", "r") as f: for palabra in leerpalabras(f): msg = oscbuildparse.OSCMessage("/texto/supercollider", ",s", palabra) osc_send(msg, "supercollider") sleep(2) osc_terminate() I've also tried with this, to see if maybe there was something wrong with my for loop (with the startup, and terminate of course): msg = oscbuildparse.OSCMessage("/texto/supercollider", ",s", "holis") osc_send(msg, "supercollider") I run the trace method on SC, nothing appears on the post window when I run the Python script on terminal, but no error appears on neither one of them, so I'm a bit lost on what I can test to make sure is getting somewhere. It doesn't print on the SC post window, it just says OSCdef(texto, /texto/supercollider, nil, nil, nil).
When I run the SuperCollider piece of your example, and then run: n = NetAddr("127.0.0.1", 57120); n.sendMsg('/texto/supercollider', 1, 2, 3); ... I see the message printed immediately (note that you used postIn instead of postln, if you don't fix that you'll get an error instead of a printed message). Like you, I don't see anything when I send via the Python library - my suspicion is that there's something wrong on the Python side? There's a hint in this response that you have to call osc_process() after sends, but that still doesn't work for me You can try three things: Run OSCFunc.trace in SuperCollider and watch for messages (this will print ALL incoming OSC messages), to see if your OSCdef is somehow not receiving messages. Try a network analyzer like Packet Peeper (http://packetpeeper.org/) to watch network traffic on your local loopback network lo0. When I do this, I can clearly see messages sent by SuperCollider, but I don't see any of the messages I send from Python, even when I send in a loop and call osc_process(). If you can't find any sign of Python sending OSC packets, try a different Python library - there are many others available.
(I'm osc4py3 author) osc4py3 store messages to send within internal lists and returns immediately. These lists are processed during osc_process() calls or directly by background threads (upon selected theading model). So, if you have selected as_eventloop threading model, you need to call osc_process() some times, like: … with open("partitura.txt", "r") as f: for palabra in leerpalabras(f): msg = oscbuildparse.OSCMessage("/texto/supercollider", ",s", palabra) osc_send(msg, "supercollider") for missme in range(4): osc_process() sleep(0.5) … See doc: https://osc4py3.readthedocs.io/en/latest/userdoc.html#threading-model
How can i show progress of node chid_process commands?
I have to show progress of node chid_process commands on UI. I am not able to track the progress of commands using any js lib like progress-bar. How can i show say "git clone" progress on UI so that user knows the status of the process ?
If you mean in general and not for functions you define specifically for this purpose and want to run separately as child process, you really can't unless the child process provides this information itself via for example STDOUT. And if so, you can only grab this raw output for then having to parse it to find something you could use to indicate progress. This of course, has its own quirks as the output is typically buffered which require you to think through how you parse the buffer(ing). On top of that you can run into cases where the output format or order changes in the future in such a way that your program no longer can find the key information it needs. In the case of git, there is really no progress per-se, only stages - which is fine and can act as a form of progress (stage 1 of 4 etc.). To grab the output you would use something like: const spawn = require("child_process").spawn; const child = spawn("git" , ["clone", "https://some.rep"]); child.stdout.on("data", data => { // parse data here... }); ... and the same for stderr. See Node documentation for more details.
Try the farmhand package. As the description goes, It is an abstration over child_process that makes it easy to run a function in the background, get its progress, result, and cancel if necessary. Hope this helps!
How to monitor keyboard events from X11
I know there has been a few of these, but a lot of the answers always to have a lot of buts, ifs, and you shouldn't do that. What I'm trying to do is have a background program that can monitor the keyboard events from X11. This is on an embedded device, and it will have a main app basically running in something like a kiosk mode. We want to have a background app that manages a few things, and probably a back doors hook. But this app generally will not have focus. I can't use the main app, because its partially there for a fail safe if the main app ever fails, or to do some dev type things to bypass the main app. The best question I found is a few years old, so I'm not sure how up to date it is. This was extremely easy to do with windows. X KeyPress/Release events capturing irrespective of Window in focus
The correct way for doing that is using Xlib. Using this library you can write code like this: while (1) { XNextEvent(display, &report); switch (report.type) { case KeyPress: if (XLookupKeysym(&report.xkey, 0) == XK_space) { fprintf (stdout, "The space bar was pressed.\n"); } break; } } // This event loop is rather simple. It only checks for an expose event. // XNextEvent waits for an event to occur. You can use other methods to get events, // which are documented in the manual page for XNextEvent. // Now you will learn how to check if an event is a certain key being pressed. // The first step is to put case KeyPress: in your switch for report.type. // Place it in a similar manner as case Expose. Also you could use poll or select on the special device file that is mapped to your keyboard. In my case is /dev/input/event1. If you have doubts about what's the special file mapped to your keyborad, read the file /var/log/Xorg.0.log (search for the word keyboard). Here you have another link of interest: Linux keyboard event capturing /dev/inputX
Automating ssh login: tcl expect interact command behaves weird
I wanted to automate ssh logins. After some research, it seemed like tcl/expect was the route to go. However, my issue is that when interact takes over my terminal, stuff doesn't work as expected (pun not intended). For example, if I resize the terminal, it does not "take". Also, sometimes the interact is not responsive, and sometimes it just hangs for no reason. I have included my code below. My question for the code is, am I missing something? Also, is there a better way to do this (with another scripting language?) I need the terminal to be very responsive, and no different than if I had manually typed ssh on the console. proc Login {username server password} { set prompt "(%|>|\#|\\\$) $" spawn /usr/bin/ssh $username#$server expect { -re "Are you sure you want to continue connecting (yes/no)?" { exp_send "yes\r" exp_continue #continue to match statements within this expect {} } -nocase "password: " { exp_send "$password\r" interact } } }
The issue you bring up about 'interact' not noticing that the window has changed size is because, by default, interact only watches the streams of characters. When you resize the window, a WINCH signal is raised. By default, Expect has the, uh, default action which is to ignore it. You should use Expect's trap command to catch the SIGWINCH. Then you can do what you want - for example, propagating the new size to the other side or taking some other local action. You can find examples in Expect's sample scripts that do this. And there is an explanation and example in the Expect book of how to handle SIGWINCH.
spawn ssh my-server.example.net trap { set rows [stty rows] set cols [stty columns] stty rows $rows columns $cols < $spawn_out(slave,name) } WINCH expect { "assword: " {send "Let-Me-In-Please\r"} "Last login" } interact
As W. Craig Trader mentions in a comment, the "right" way to do this is to use ssh-keygen to generate a key for authentication. You can avoid the "continue" prompt by setting -o StrictHostKeyChecking=no.