lpty is a module that allows a program written in lua to open the master side of a PTY and start a program with the slave side of the PTY as its controlling terminal. The PTY may then be read from and written to, thus controlling the remote program.
added getfd method to retrieve the file descriptor of the pty's master side. This has been contributed by Matthew Wild (mwild1 at gmail dot com).
His rationale, which I can completely get behind, is this:
Having the method name 'getfd' is good, as it makes the pty objects compatible with LuaSocket objects. This means you can pass the pty directly to socket.select()! (it probably works with LuaEvent too, but I haven't tested).
I have tested it with luaposix' poll() and that works fine.
You may also want to read up on how PTYs work by consulting the pty(7) manpage. A more extensive treatment of the matter can be found here
You can get lpty-1.0.1 by clicking on this link, or by installing it from the luarocks repository. If you fetch it from here, the included README gives hints on how to build it.
The lpty module and all accompanying documentation and additional source code is released under the MIT/X11 license.
Copyright (c) 2010-2013 Gunnar Zötl <email@example.com> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
If you have anything to say about this, comments, bug reports, whatever, feel free to email them to firstname.lastname@example.org