cygwin 3.1.2 + Windows 10 Home Build 10.0.18362 - alt+space hotkeys not working

2019-12-24 Thread Eugene Klimov
after upgrade cygwin to latest 3.1.2 (mintty i have following bugs alt+space hotkeys not working in any cygwin applications screen inside cygwin ssh have wrong tab completion i try get help on IRC freenode, but nobody answer me ;-( Is anybody here who have same bugs as me? -- Problem reports:

Re: startx cygwin

2019-12-24 Thread Brian Inglis
On 2019-12-24 16:11, Sanjay Gupta wrote: > starting startx following error > Unable to init server: Could not connect to 127.0.0.1: Connection refused > > while startxwin runs fine ( I see X server listening) > > > Welcome to the XWin X Server > Vendor: The Cygwin/X Project > Release: 1.20.5.0

startx cygwin

2019-12-24 Thread Sanjay Gupta
starting startx following error Unable to init server: Could not connect to 127.0.0.1: Connection refused while startxwin runs fine ( I see X server listening) Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.20.5.0 OS: CYGWIN_NT-10.0-18362 USD61FFDZ1 3.1.2-340.x86_64

[PATCH] Cygwin: fhandler_socket::open: set errno according to POSIX

2019-12-24 Thread Ken Brown
Set errno to EOPNOTSUPP instead of ENXIO when 'open' is called on a socket. This is consistent with POSIX, starting with the 2016 edition. Earlier editions were silent on this issue. --- winsup/cygwin/fhandler_socket.cc | 2 +- winsup/cygwin/release/3.1.3 | 5 +

Re: Files created with CYGWIN have "NULL SID:(DENY)" windows ACL, inter alia

2019-12-24 Thread Andrey Repin
Greetings, Peter Binney! > Hello Andrey - many thanks for that. I have now removed /etc/passwd > and /etc/group which didn't change anything. > I read some of your earlier posts on this and had already tried the noacl > route. > Unfortunately it has made no difference. I added a second line to

Re: A permissions puzzle

2019-12-24 Thread Andrey Repin
Greetings, Eliot Moss! > On 12/22/2019 7:34 AM, Andrey Repin wrote: >> Drive has specific network path, use it. > Thank you, Andrey, but with (admittedly minimal) searching and > playing around, I could not figure out how to determine what > that path is. This is a locally attached (USB)