This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: is-cygwin-tty check
- From: Mihail Konev <k dot mvc at ya dot ru>
- To: cygwin-developers at cygwin dot com
- Date: Sat, 12 Nov 2016 16:07:52 +0500
- Subject: Re: is-cygwin-tty check
- Authentication-results: sourceware.org; auth=none
- Authentication-results: smtp3h.mail.yandex.net; dkim=pass header.i=@ya.ru
- References: <20161112022046.GD2193@localhost> <20161112023426.GE2193@localhost> <20161112091142.GB3744@calimero.vinschen.de>
The first word was allowed to be [a-z0-9]* to allow for any future cygwin fork.
Sticking to cygwin/msys.
Now pipe name would be checked for being
(cygwin|msys)-[a-z0-9]{16}-pty[0-9]+-(to|from)-master
Should the "to-master-cyg" pipe be considered tty?
Assuming that "master-ctl" and "echoloop" do not.
Also, there are
winsup/cygwin/dtable.cc: char std[3][sizeof ("/dev/ptyNNNN")];
winsup/cygwin/fhandler_tty.cc: char buf[sizeof ("opened pty master for ptyNNNNNNNNNNN")];
winsup/cygwin/fhandler_tty.cc: char pipename[sizeof("ptyNNNN-to-master-cyg")];
winsup/cygwin/tty.cc: char pipename[sizeof("ptyNNNN-from-master")];
Should the "pty[0-9]+" be "pty[0-9]{1,4}" ?