Clark Wang

The current behavior is intentional. I don't want people to think that the following usage would work as expected: ~~~ passh cmd1 ... | cmd2 ... ~~~ Simple example: ~~~...

That's intentional. When you start typing it enters interactive mode automatically. That's because it cannot tell at what time the users want to enter interactive mode. Manual intervention is a...

For now `send -file` only accepts a regular file. `send` sets a limit and at most 1024 bytes can be sent so it need to check the file size before...

OK. Let me see if I can remove the regular file check.

May be like this: * `send -file FILE [-limit COUNT]` * *FILE* can be `-` which means *stdin*. * If `-limit COUNT` is not specified, *FILE* must be a regular...

It's now available on the "devel" branch. Will merge to "master" after the doc is updated and tests are added.

> That's impressive, thanks! Testing it now: > > ``` > $ ./sexpect -s /tmp/sp.sock send -fd [ERROR] invalid number: /dev/fd/63 > ``` > > Probably makes sense to accept...

> When I'm trying to use stdio, I have to hit extra Enter to make dmenu pop up: > > ``` > ./sexpect -s /tmp/sp.sock send -file - -limit 32...

Don't bother. Users can just `sexpect spawn sh -c ...`

I still have this problem (`Right Option acts as Control` does not work) with `10.9.5`. Anyone has a workaround?