Conversation
|
Thanks for letting me know. It may be a few weeks but I will check this out and merge in. I have a Mac here that I can test on. The script was not designed for portability away from Linux, so I'm surprised it works. Mac is still on ancient BASH 3.x too, and I'm prone to use BASH 4 features without thinking about it. The cu device is an old unix thing related to the tip and cu utilities. I think it stood for "call unix", and was basically a null modem kind of thing. It's a raw device, whereas the tty device has some settings designed for terminals that is probably mucking things up. |
|
Perhaps it is not as straight forward as I thought. I'll be sure to post any useful findings. |
|
Figured out the problem. My initial test was working because I had |
Good news - your script works on macOS!
I only had to make a minor modification for the macOS version of stty.
The device file that worked was
/dev/cu.usbmodem1461(worth putting in readme). Don't really understand at the moment why using/dev/tty.usbmodem1461was not working. I haven't investigated a way to set device file permissions on Mac, if even possible. Just used sudo:Awesome! Nice work, @CapitalF 🍾 🍰 👍