Fork me on GitHub
#membrane-term
<
2021-11-17
>
lread02:11:38

Another musing: I think that the line-delay and final-delay options do the job, but was wondering if we might consider something more refined. The idea is to maybe allow directives in play scripts. First thought: something that would allow you to wait for specific text (ex. user=>) before proceeding. But maybe I’m re-inventing AppleScript or something? I dunno.

phronmophobic03:11:22

at that point, why not just run a clojure script?

phronmophobic03:11:59

I'd be more inclined to add something like bb support than create a mini dsl

lread03:11:13

Yeah maybe. I was thinking of maybe employing sci somehow to hook in and wait for interesting events. This was with screenshots in mind. But ya know what? The delay options are maybe a bit general but they do the job, yeah?

phronmophobic03:11:35

if there's a good use case in mind, then it could make sense. just trying to not fall into the trap where you had some extra keywords, then loops, then variables, then functions, etc.

phronmophobic03:11:42

scripting on top of a human api is always tricky. if there's a way to improve the programmatic API of either membrane.term or the tool you're trying to screen cap, then that might be another route

phronmophobic03:11:25

one similar idea I had was to have a "record" feature where you just use the terminal normally and you have tools for exporting the playback however you want

phronmophobic03:11:57

or you could record as you use the terminal normally and it can also store the timings of your inputs that you could use as a play script

lread03:11:29

Yeah good points. I'll ponder (maybe). Was thinking of hooking with maybe sci somehow. But realize this can get really over-complicated quickly.

phronmophobic03:11:10

I've used selenium in the past to script web pages and sometimes it's what you have to do, but it's not usually much fun

phronmophobic03:11:41

the wait for matching input reminded me of that

lread03:11:48

Yeah reminded me of selenium too.