Re: IDP.Generic virus reported in okular.exe, attention: Yaakov Selkowitz
Hi, Not sure how and where do you look, but Google gave me this https://www.avg.com/en-us/false-positive-file-form Please file the report there On Sat, Sep 7, 2019, 11:25 PM Alan Thwaits wrote: > Dear Cygwin community, > > I have looked and looked. I cannot find an appropriate place to report > viruses. I know of two viruses, and I would like to report them. > > Sincerely, > > Alan > > > On Sat, Sep 7, 2019 at 8:20 AM Andrey Repin wrote: > > > Greetings, Alan Thwaits! > > > > > Dear Yaakov or other interested maintainer: > > > > > When I ran the program okular.exe under bash and xterm, my antivirus > > > program AVG Antivirus Free quarantined the program and reported that it > > > contains the virus IDP.Generic. > > > > > I hope that you find this helpful. > > > > Why do you report it here? > > Report to AVG support. > > If they confirm that it is indeed a virus, and not a failed heuristic, > then > > you can raise an issue here. > > > > > > -- > > With best regards, > > Andrey Repin > > Saturday, September 7, 2019 5:33:57 > > > > Sorry for my terrible english... > > > > > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cURL uploads 0 length file for sftp transfer.
I upgraded to the latest version curl 7.65.3 with libcurl 7.65.3, same issue. curl 7.65.3 (i686-pc-cygwin) libcurl/7.65.3 OpenSSL/1.1.1c zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.0.4) libssh/0.8.7/openssl/zlib nghttp2/1.37.0 Thanks. On Friday, September 6, 2019, 3:44:13 PM EDT, ALbert wrote: We recently upgraded cURL from version:curl 7.50.3 (i686-pc-cygwin) libcurl/7.50.3 OpenSSL/1.0.2j zlib/1.2.8 libidn/1.29 libpsl/0.14.0 (+libidn/1.29) libssh2/1.7.0 nghttp2/1.14.0tocurl 7.64.1 (i686-pc-cygwin) libcurl/7.65.3 OpenSSL/1.1.1c zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.0.4) libssh/0.8.7/openssl/zlib nghttp2/1.37.0 Since the upgrade, we've seen problems uploading text files to sftp servers. Here's the call that we make: curl--trace-ascii trace.txt -k sftp://:@/file.txt-T file.txt On initial call, a 0-length file is uploaded, with successful return code. On immediate rerun, a full file is uploaded (if we wait few minutes, 0-length file will get uploaded). Below are the traces from initial and subsequent calls. We also tried using same version curl on a linux box, without any issues. We also downloaded latest version of curl from curl for Windows, "curl 7.65.3 (i386-pc-win32) libcurl/7.65.3 OpenSSL/1.1.1c (Schannel) zlib/1.2.11 brotli/1.0.7 WinIDN libssh2/1.9.0 nghttp2/1.39.2", and its also working correctly. Unfortunately, the server we're uploading to belongs to a client, and we can't see if this is an issue on a server side. However, even if it was, why would linux curl and windows curl (from curl.haxx.se) would work correctly? Any help or pointers would be appreciated. Thank you. Here's the trace files: >From initial call:== Info: STATE: INIT => CONNECT handle 0x80068340; line 1356 >(connection #-5000) == Info: Added connection 0. The cache now contains 1 members == Info: STATE: CONNECT => WAITRESOLVE handle 0x80068340; line 1397 (connection #0) == Info: Trying XXX.XX.XX.XX...== Info: TCP_NODELAY set == Info: STATE: WAITRESOLVE => WAITCONNECT handle 0x80068340; line 1476 (connection #0) == Info: Connected to XXX ( XXX.XX.XX.XX) port 22 (#0)== Info: STATE: WAITCONNECT => SENDPROTOCONNECT handle 0x80068340; line 1532 (connection #0) == Info: Marked for [keep alive]: SSH default == Info: User: Opus_efg == Info: SSH 0x80048f90 state change from SSH_STOP to SSH_INIT (line 2115) == Info: SSH 0x80048f90 state change from SSH_INIT to SSH_S_STARTUP (line 582) == Info: STATE: SENDPROTOCONNECT => PROTOCONNECT handle 0x80068340; line 1547 (connection #0) == Info: SSH 0x80048f90 state change from SSH_S_STARTUP to SSH_HOSTKEY (line 595) == Info: SSH 0x80048f90 state change from SSH_HOSTKEY to SSH_AUTHLIST (line 605) == Info: SSH 0x80048f90 state change from SSH_AUTHLIST to SSH_AUTH_PKEY_INIT (line 628) == Info: Authentication using SSH public key file == Info: SSH 0x80048f90 state change from SSH_AUTH_PKEY_INIT to SSH_AUTH_KEY_INIT (line 697) == Info: SSH 0x80048f90 state change from SSH_AUTH_KEY_INIT to SSH_AUTH_KEY (line 743) == Info: completed keyboard interactive authentication == Info: SSH 0x80048f90 state change from SSH_AUTH_KEY to SSH_AUTH_DONE (line 761) == Info: Authentication complete == Info: SSH 0x80048f90 state change from SSH_AUTH_DONE to SSH_SFTP_INIT (line 807) == Info: SSH 0x80048f90 state change from SSH_SFTP_INIT to SSH_SFTP_REALPATH (line 833) == Info: SSH CONNECT phase done == Info: SSH 0x80048f90 state change from SSH_SFTP_REALPATH to SSH_STOP (line 850) == Info: STATE: PROTOCONNECT => DO handle 0x80068340; line 1566 (connection #0) == Info: DO phase starts == Info: SSH 0x80048f90 state change from SSH_STOP to SSH_SFTP_QUOTE_INIT (line 2332) == Info: SSH 0x80048f90 state change from SSH_SFTP_QUOTE_INIT to SSH_SFTP_GETINFO (line 868) == Info: SSH 0x80048f90 state change from SSH_SFTP_GETINFO to SSH_SFTP_TRANS_INIT (line 1060) == Info: SSH 0x80048f90 state change from SSH_SFTP_TRANS_INIT to SSH_SFTP_UPLOAD_INIT (line 1080) == Info: SSH 0x80048f90 state change from SSH_SFTP_UPLOAD_INIT to SSH_SFTP_CLOSE (line 1143) == Info: STATE: DO => DOING handle 0x80068340; line 1608 (connection #0) == Info: SFTP DONE done == Info: SSH 0x80048f90 state change from SSH_SFTP_CLOSE to SSH_STOP (line 1651) == Info: DO phase is complete == Info: STATE: DOING => DO_DONE handle 0x80068340; line 1693 (connection #0) == Info: STATE: DO_DONE => PERFORM handle 0x80068340; line 1743 (connection #0) == Info: STATE: PERFORM => DONE handle 0x80068340; line 1933 (connection #0) == Info: multi_done == Info: SSH 0x80048f90 state change from SSH_STOP to SSH_SFTP_CLOSE (line 2390) == Info: SFTP DONE done == Info: SSH 0x80048f90 state change from SSH_SFTP_CLOSE to SSH_STOP (line 1651) == Info: Connection #0 to host XXX left intact Trace from subsequent call:== Info: STATE: INIT => CONNECT handle 0x80068340; line 1356 (connection #-5000) == Info: Added connection 0. The cache now contains 1 members == Info: STATE: CONNECT => WAIT
Re: cURL uploads 0 length file for sftp transfer.
On 2019-09-06 14:17, Yaakov Selkowitz wrote: > On Fri, 2019-09-06 at 19:44 +, ALbert via cygwin wrote: >> We recently upgraded cURL from version:curl 7.50.3 (i686-pc-cygwin) >> libcurl/7.50.3 OpenSSL/1.0.2j zlib/1.2.8 libidn/1.29 libpsl/0.14.0 >> (+libidn/1.29) libssh2/1.7.0 nghttp2/1.14.0 to curl 7.64.1 (i686-pc- >> cygwin) libcurl/7.65.3 OpenSSL/1.1.1c zlib/1.2.11 brotli/1.0.7 >> libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.0.4) >> libssh/0.8.7/openssl/zlib nghttp2/1.37.0 > > Am I reading this right, curl 7.64.1 with libcurl 7.65.3? Those > versions should match exactly. > >> Since the upgrade, we've seen problems uploading text files to sftp servers. >> Here's the call that we make: >> curl--trace-ascii trace.txt -k sftp://:@/file.txt-T >> file.txt >> >> On initial call, a 0-length file is uploaded, with successful return code. >> On immediate rerun, a full file is uploaded (if we wait few minutes, >> 0-length file will get uploaded). Below are the traces from initial and >> subsequent calls. We also tried using same version curl on a linux box, >> without any issues. We also downloaded latest version of curl from curl for >> Windows, "curl 7.65.3 (i386-pc-win32) libcurl/7.65.3 OpenSSL/1.1.1c >> (Schannel) zlib/1.2.11 brotli/1.0.7 WinIDN libssh2/1.9.0 nghttp2/1.39.2", >> and its also working correctly. >> Unfortunately, the server we're uploading to belongs to a client, and we >> can't see if this is an issue on a server side. However, even if it was, why >> would linux curl and windows curl (from curl.haxx.se) would work correctly? >> Any help or pointers would be appreciated. Thank you. > > Make sure you are using all the latest packages, especially that you > have the latest and matching versions of curl and libcurl, and try > again. FYI Cygwin curl current version produces: $ curl --version curl 7.65.3 (x86_64-pc-cygwin) libcurl/7.65.3 OpenSSL/1.1.1c zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.0.4) libssh/0.8.7/openssl/zlib nghttp2/1.37.0 Release-Date: 2019-07-19 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp Features: AsynchDNS brotli Debug GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz Metalink NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP TrackMemory UnixSockets -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Command line processing in dcrt0.cc does not match Microsoft parsing rules
On 2019-09-05 16:01, Stephen Provine via cygwin wrote: > On 9/5/19 2:05 PM, Eric Blake wrote: >> On 9/5/19 1:31 PM, Stephen Provine via cygwin wrote: >>> Not expected. > >> Why not? That obeyed cmd's odd rules: The moment you have a " in the >> command line, that argument continues until end of line or the next " >> (regardless of how many \ precede the "). > > Now I'm really confused. Brian seemed to indicate that the POSIX rules were > followed, but you're indicating that the Windows command line parsing rules > are followed. So I assume the reality is that it is actually some mix of the > two. > Is the effective parsing logic implemented by Cygwin documented anywhere? Depends on what you are running thru - you have layers - in that test case you ran from cmd, so cmd parsing has to be first taken into account, before passing the resulting command line to bash, where Cygwin will construct a POSIX argument list from cmd output, and pass that to bash then script.sh. Try your testing using my script.sh shown earlier, and call bash with -vx options for debugging output. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: zstd-1.4.3-1 and development headers / libraries
This release updates Zstandard to the latest upstream version, which is a maintenance release. Zstandard, or zstd as short version, is a fast lossless compression algorithm, targeting real-time compression scenarios at zlib-level and better compression ratios. http://www.zstd.net/ Besides a standalone compression tool, development headers and a library with comprehensive API are available both for Cygwin native applications and cross-compilation toolchains in the following sub-packages: libzstd-devel-1.4.3-1 libzstd1-1.4.3-1 mingw64-i686-zstd-1.4.3-1 mingw64-x86_64-zstd-1.4.3-1 Note This version is compiled with support for GZip, LZ4 and Xz compression. Support for legacy formats from versions before 1.0 has been removed. -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: libcerf-1.13-1
This is an update to the latest upstream version. Libcerf is a self-contained numeric library that provides an efficient and accurate implementation of complex error functions, along with Dawson, Faddeeva, and Voigt functions. -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Issues with multiple displays and openGL libraries after latest updates to X, GL, and Mesa
I was starting with "startxwin &" in the Cygwin terminal. Is this the wrong way to do it? I'll try that soon and get back to you. This was before the latest set of updates to Xorg and the openGL libraries, so it could be that it had something to do with the missing libEGL dependency - I will try again now, and hopefully it will work :). If it's any help, I'm running Cygwin on Windows 7. Hamish On 07/09/2019 16:11, Jon Turney wrote: > On 05/09/2019 11:28, Hamish MB wrote: >> libraries. Additionally, the xwin server refuses to start if more than >> one display is present, for reasons I don't understand. > > That is unusual. > > I assume you are trying to start via the start menu shortcut? > > Does starting it as 'XWin -multiwindow' work? > > If not, can you provide the /var/log/xwin/XWin.0.log? >
[ANNOUNCEMENT] Updated: cfitsio-3.470-1
[re-sent with correct subject line] This is an update to the latest upstream version. cfitsio-3.470-1 mingw64-i686-cfitsio-3.470-1 mingw64-x86_64-cfitsio-3.470-1 Notes - The library ABI version has changed from libcfitsio3 to libcfitsio7. Packages depending on libcfitsio should be recompiled to make use of the newer ABI. The build now enables BZip2, cURL and multithreading support. The build again provides the mingw64 packages. -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: cfitsio-3.450-1
This is an update to the latest upstream version. cfitsio-3.470-1 mingw64-i686-cfitsio-3.470-1 mingw64-x86_64-cfitsio-3.470-1 Notes - The library ABI version has changed from libcfitsio3 to libcfitsio7. Packages depending on libcfitsio should be recompiled to make use of the newer ABI. The build now enables BZip2, cURL and multithreading support. The build again provides the mingw64 packages. -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: retry: Problem transfering X11 cut/copy buffer to windows and back
On 26/08/2019 02:57, L A Walsh wrote: Starting a few days ago, after an update to cygwin, I'm finding it impossible to transfer my xselection from cygwin X to any Win application or vice versa. Are you using xorg-server 1.20.5-1 or later test release package? I made some significant changes to the clipboard code in that, as noted in the announce mail [1]. [1] https://cygwin.com/ml/cygwin-announce/2019-06/msg9.html I've tried multpile Windows apps (Windows 7 SP1 x64) and multiple X apps and no go. I first noticed it in gvim -- which I run on my linux box and display via 'X' locally. The only thing I noticed w/X,u has been a checkmarked value about Clipboard may use primary selection (which is checked, though I tried both ways). Having to write things out ot files is royal pain, so any ideas would be very appreciated. -- Jon Turney Volunteer Cygwin/X X Server maintainer -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: multiple displays support for XFCE
On 03/09/2019 07:51, Jürgen Weber wrote: Hi, got a two display Windows 10 system here. I'm using the XFCE desktop started with startxfce4. The whole desktop is in one Windows 10 toplevel window, that I can move to either one of the displays. Can you make XFCE full screen over both displays? Sure, try 'startxfce4 -- -multimonitors' Or can you start two XFCE desktop windows, one for each of the displays? Something like 'startxfce4 -- -screen 0 @1 -screen 1 @2' should be what you want there, but xfce doesn't seem to use the 2nd screen window (so perhaps some additional configuration to xfce is needed there...) The options after the double dash are provided to the X server, XWin. See 'man XWin' for more details. -- Jon Turney Volunteer Cygwin/X X Server maintainer -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: IDP.Generic virus reported in okular.exe, attention: Yaakov Selkowitz
Dear Cygwin community, I have looked and looked. I cannot find an appropriate place to report viruses. I know of two viruses, and I would like to report them. Sincerely, Alan On Sat, Sep 7, 2019 at 8:20 AM Andrey Repin wrote: > Greetings, Alan Thwaits! > > > Dear Yaakov or other interested maintainer: > > > When I ran the program okular.exe under bash and xterm, my antivirus > > program AVG Antivirus Free quarantined the program and reported that it > > contains the virus IDP.Generic. > > > I hope that you find this helpful. > > Why do you report it here? > Report to AVG support. > If they confirm that it is indeed a virus, and not a failed heuristic, then > you can raise an issue here. > > > -- > With best regards, > Andrey Repin > Saturday, September 7, 2019 5:33:57 > > Sorry for my terrible english... > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: Perl distributions
The following Perl distributions have been updated to their latest version on CPAN, respectively: x86/x86_64 -- perl-Win32-API-0.84-2 (bugfix) noarch -- perl-Date-Manip-6.78-1 perl-File-Find-Object-0.3.4-1 perl-HTTP-Daemon-6.06-1 perl-Net-DNS-1.21-1 perl-Test-Simple-1.302168-1 perl-Test2-Suite-0.000126-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Issues with multiple displays and openGL libraries after latest updates to X, GL, and Mesa
On 05/09/2019 11:28, Hamish MB wrote: libraries. Additionally, the xwin server refuses to start if more than one display is present, for reasons I don't understand. That is unusual. I assume you are trying to start via the start menu shortcut? Does starting it as 'XWin -multiwindow' work? If not, can you provide the /var/log/xwin/XWin.0.log? -- Jon Turney Volunteer Cygwin/X X Server maintainer -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: perl-Win32-API package problem
SJ Luo writes: > I have a small Perl program that utilize module > Win32::API::Callback. Sorry that it took so long, but the problem should be fixed with the new release of that package. Please confirm that it works for your application when you get the chance to test, thank you. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: IDP.Generic virus reported in okular.exe, attention: Yaakov Selkowitz
Greetings, Alan Thwaits! > Dear Yaakov or other interested maintainer: > When I ran the program okular.exe under bash and xterm, my antivirus > program AVG Antivirus Free quarantined the program and reported that it > contains the virus IDP.Generic. > I hope that you find this helpful. Why do you report it here? Report to AVG support. If they confirm that it is indeed a virus, and not a failed heuristic, then you can raise an issue here. -- With best regards, Andrey Repin Saturday, September 7, 2019 5:33:57 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Command line processing in dcrt0.cc does not match Microsoft parsing rules
Greetings, Stephen Provine! > On 2019-09-04 23:29, Brian Inglis wrote: >> As standard on Unix systems, just add another level of quoting for each >> level of >> interpretation, as bash will process that command line, then bash will >> process >> the script command line. > My mistake - I'm very aware of the quoting rules, yet in my test script for > this > scenario I forgot to quote the arguments. However, if POSIX rules are being > implemented, there is still something I didn't expect. Here's my bash script: > #!/bin/bash > echo "$1" > echo "$2" > echo "$3" > And I invoke it like this from a Windows command prompt: > C:\> bash -x script.sh foo bar\"baz bat > + echo foo > foo > + echo 'bar\baz bat' > bar\baz bat > + echo '' > Not expected. Called from within Cygwin, the behavior is correct: Again, fully expected. > $ bash -x script.sh foo bar\"baz bat > + echo foo > foo > + echo 'bar"baz' > bar"baz > + echo bat > bat > Can you explain this difference? CMD escape character is ^, not \ > The reason I ask is that if this worked, > the way Go constructs the command line string would be just fine. No. -- With best regards, Andrey Repin Friday, September 6, 2019 23:33:46 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.3
Am 07.09.2019 um 05:32 schrieb Takashi Yano: On Fri, 6 Sep 2019 12:02:36 +0200 Thomas Wolff wrote: A tool that sets up conpty itself (rawpty from https://github.com/Biswa96/wslbridge2) does not work anymore with conpty-enabled cygwin. This suggest that double-conpty enabling may be interfering. Unfortunately, I have not yet had the time to checkout the patch code in detail, but my suspicion is that conpty may be enabled always, while it should in fact be activated only if a non-cygwin program is run. Please check out on this. I have not looked into this yet, but as you might expect, the pseudo console is always enabled behind even if it is not used. Owing to this, a cygwin program which directly accesses the console, as your previous test case, can work normally by just switching the r/w pipe to pseudo console side. I guess you are right. We are having different use cases. For the generic case, the always-enabled conpty support is probably the best solution. However, there are exceptions. One particular case is the gateway to WSL (wslbridge, wslbridge2, hvpty). When you run WSL from cygwin with conpty enabled, unfortunately, the pseudo console will enforce MS's idea of what a terminal is, i.e., it handles escape sequences, does not pass everthing through, responds to enquiry sequences itself, so the terminal cannot even report itself as mintty (or whatever) anymore. This unfortunate situation may hopefully resolve once they provide conpty "passthrough mode" as discussed in https://github.com/microsoft/terminal/issues/1173 and also in https://github.com/mintty/wsltty/issues/171#issuecomment-526778377. So there is need to switch off conpty support for certain applications, e.g. via the CYGWIN environment variable. Please consider. Thomas -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple