On Sat, Jan 13, 2024 at 09:32:44PM +0000, phoebus phoebus wrote: > Hello, > > I understand that the situation may seem complex and i apologize if my > previous messages did not provide a clear overview of the problem. Allow me > to summarize our current situation. > In this response, I will incorporate the various comments made by Greg, > Charles Tomas, and incorporate a significant portion of Greg's excellent > summary.
[...] Thanks for the detailed explanation -- and no need to apologize. Elephants are complex beasts :-) This was to me at least a delightful example of trying to come to a common understanding "Ah, yes, you're right: this feels like a trunk!". Thank you for your patience, too. One viable approach is the one proposed by Stefan et al (modify an existing terminal emulator). I'd tend to separate concerns and just write the application part as a separate process accepting a bidi connection to SSH, one to a terminal emulator, and one to the serial port (OK, some error and diagnostic logging too). The classical thing built around a select() loop, with some extended state automaton in it. And this is where I disagree with Greg (what doesn't happen very often). Some of us do love elephants :-) Cheers -- t
signature.asc
Description: PGP signature
