Re: *shell* buffer freezes within Cygwin and Emacs 27.1
On Thu, Feb 4, 2021 at 11:22 AM Ken Brown via Cygwin wrote: > [Please don't top-post on this list. Thanks.] > > On 2/4/2021 11:54 AM, Randy Galbraith via Cygwin wrote: > > Good morning Takashi. > > > > Thank you so much for your response. I just tried: > > > > env CYGWIN=disable_pcon emacs-q > > > > and cmd input/output works again. I'll now need to document this for our > > team and seek out what this does. > > In case it wasn't clear to you from Takashi's suggestion to try a > snapshot, this > problem has already been fixed for the next cygwin release. Setting > CYGWIN=disable_pcon is just a temporary workaround. It would be great if > you > would test a snapshot and confirm the fix. > > Ken > Hi Ken. Regarding "top posting" my apologies. I have limited experience interacting with an email list. I issued a reply-all via Gmail within Firefox on Ubuntu. Hopefully this reply is better. This reply is following some stackoverflow advice on avoiding top-posting while using Gmail. Thanks for the information on the setting being temporary. I will see what I can do to test the snapshot. I am somewhat limited in what I can do given this copy of Windows 10 is hosted in a corporate environment where I have limited ability to download and install items, as well as, of course to justify work-time spent on problem resolution. Kind regards, -Randy -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: *shell* buffer freezes within Cygwin and Emacs 27.1
[Please don't top-post on this list. Thanks.] On 2/4/2021 11:54 AM, Randy Galbraith via Cygwin wrote: Good morning Takashi. Thank you so much for your response. I just tried: env CYGWIN=disable_pcon emacs-q and cmd input/output works again. I'll now need to document this for our team and seek out what this does. In case it wasn't clear to you from Takashi's suggestion to try a snapshot, this problem has already been fixed for the next cygwin release. Setting CYGWIN=disable_pcon is just a temporary workaround. It would be great if you would test a snapshot and confirm the fix. Ken -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: *shell* buffer freezes within Cygwin and Emacs 27.1
Good morning Takashi. Thank you so much for your response. I just tried: env CYGWIN=disable_pcon emacs-q and cmd input/output works again. I'll now need to document this for our team and seek out what this does. Kind regards, -Randy On Wed, Feb 3, 2021 at 5:08 PM Takashi Yano wrote: > On Wed, 3 Feb 2021 15:45:36 -0700 > Randy Galbraith via Cygwin wrote: > > Hi Everyone. > > > > Please note: I attempted to post this message from my work > > email. I do not believe it every arrived. > > > > My long used work flow has recently stopped working. I'm trying to > > understand why and how it could be resolved. The failing steps are: > > > > Cygwin64 Terminal (bash prompt) > > startx -- :1 -multiwindow -clipboard & > > xterm > > emacs -q > > M-x shell > > $ cmd > > > > I expect to get a Windows 10 command prompt that works. Instead the shell > > buffer display cmd output incorrectly formatted (e.g. extra white space) > > and when I type a command like dir it freezes. > > > > I suspect this may be an issue related to a recent Windows 10 update > > that in turn has changed the way cmd interacts with Cygwin bash and > > Emacs. I have completed a re-install to the latest version (as of > > 2/1/2021). Alas, this did not resolve the problem. > > > > ** details ** > > $ uname -r > > 3.1.7(0.340/5/3) > > GNU Emacs 27.1 (build 1, x86_64-pc-cygwin, GTK+ Version 3.22.28) > > of 2020-10-29 > > ** details end ** > > > > See below for *shell* buffer and cygcheck output. > > > > Kind regards, > > -Randy Galbraith > > > > ** *shell* buffer ** > > ^[]0;~^G > > x@xxx ~ > > $ cmd > > > > > > $ Microsoft Windows [Version 10.0.17763.1697] > > (c) 2018 Microsoft Corporation. All rights reserved. > > > > C:\cygwin64\home\x>dir > > dir > > ^ frozen at this point > > ** *shell* buffer end ** > > Please try latest cygwin snapshot. > https://cygwin.com/snapshots/ > > Or > env CYGWIN=disable_pcon emacs -q > instead of just > emacs -q > > -- > Takashi Yano > -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: *shell* buffer freezes within Cygwin and Emacs 27.1
On Wed, 3 Feb 2021 15:45:36 -0700 Randy Galbraith via Cygwin wrote: > Hi Everyone. > > Please note: I attempted to post this message from my work > email. I do not believe it every arrived. > > My long used work flow has recently stopped working. I'm trying to > understand why and how it could be resolved. The failing steps are: > > Cygwin64 Terminal (bash prompt) > startx -- :1 -multiwindow -clipboard & > xterm > emacs -q > M-x shell > $ cmd > > I expect to get a Windows 10 command prompt that works. Instead the shell > buffer display cmd output incorrectly formatted (e.g. extra white space) > and when I type a command like dir it freezes. > > I suspect this may be an issue related to a recent Windows 10 update > that in turn has changed the way cmd interacts with Cygwin bash and > Emacs. I have completed a re-install to the latest version (as of > 2/1/2021). Alas, this did not resolve the problem. > > ** details ** > $ uname -r > 3.1.7(0.340/5/3) > GNU Emacs 27.1 (build 1, x86_64-pc-cygwin, GTK+ Version 3.22.28) > of 2020-10-29 > ** details end ** > > See below for *shell* buffer and cygcheck output. > > Kind regards, > -Randy Galbraith > > ** *shell* buffer ** > ^[]0;~^G > x@xxx ~ > $ cmd > > > $ Microsoft Windows [Version 10.0.17763.1697] > (c) 2018 Microsoft Corporation. All rights reserved. > > C:\cygwin64\home\x>dir > dir > ^ frozen at this point > ** *shell* buffer end ** Please try latest cygwin snapshot. https://cygwin.com/snapshots/ Or env CYGWIN=disable_pcon emacs -q instead of just emacs -q -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
*shell* buffer freezes within Cygwin and Emacs 27.1
Hi Everyone. Please note: I attempted to post this message from my work email. I do not believe it every arrived. My long used work flow has recently stopped working. I'm trying to understand why and how it could be resolved. The failing steps are: Cygwin64 Terminal (bash prompt) startx -- :1 -multiwindow -clipboard & xterm emacs -q M-x shell $ cmd I expect to get a Windows 10 command prompt that works. Instead the shell buffer display cmd output incorrectly formatted (e.g. extra white space) and when I type a command like dir it freezes. I suspect this may be an issue related to a recent Windows 10 update that in turn has changed the way cmd interacts with Cygwin bash and Emacs. I have completed a re-install to the latest version (as of 2/1/2021). Alas, this did not resolve the problem. ** details ** $ uname -r 3.1.7(0.340/5/3) GNU Emacs 27.1 (build 1, x86_64-pc-cygwin, GTK+ Version 3.22.28) of 2020-10-29 ** details end ** See below for *shell* buffer and cygcheck output. Kind regards, -Randy Galbraith ** *shell* buffer ** ^[]0;~^G x@xxx ~ $ cmd $ Microsoft Windows [Version 10.0.17763.1697] (c) 2018 Microsoft Corporation. All rights reserved. C:\cygwin64\home\x>dir dir ^ frozen at this point ** *shell* buffer end ** ** cygcheck output ** Cygwin Configuration Diagnostics Current System Time: Tue Feb 02 18:21:31 2021 Windows 10 Enterprise Ver 10.0 Build 17763 Path: C:\cygwin64\usr\local\bin C:\cygwin64\bin C:\cygwin64\home\x\bin C:\Windows\system32 C:\Windows C:\Program Files\Git\cmd Output from C:\cygwin64\bin\id.exe SysDir: C:\WINDOWS\system32 WinDir: C:\WINDOWS USER = 'x' PWD = '/home/x' HOME = '/home/x' HKEY_CURRENT_USER\Software\Cygwin HKEY_CURRENT_USER\Software\Cygwin\Installations (default) = '\??\C:\cygwin64' HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\DefaultIcon (default) = 'C:\cygwin64\bin\xlaunch.exe.exe,1' HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Edit HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Edit\command (default) = '"C:\cygwin64\bin\run.exe" --quote "C:\cygwin64\bin\bash.exe" -l -c "xlaunch -load \"$(cygpath '%1')\""' HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Open HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Open\command (default) = '"C:\cygwin64\bin\run.exe" --quote "C:\cygwin64\bin\bash.exe" -l -c "xlaunch -run \"$(cygpath '%1')\""' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations (default) = '\??\C:\cygwin64' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup (default) = 'C:\cygwin64' HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Tanium\Tanium Client\Sensor Data\Applications\cygwin-console-helper obcaseinsensitive set to 1 Cygwin installations found in the registry: System: Key: Path: C:\cygwin64 User: Key: Path: C:\cygwin64 c: hd NTFS xxMb 67% CP CS UN PA FC QU OSDisk d: cd N/A N/A C:\cygwin64 / system binary,auto C:\cygwin64\bin /usr/bin system binary,auto C:\cygwin64\lib /usr/lib system binary,auto cygdrive prefix /cygdrive user binary,posix=0,auto Found: C:\cygwin64\bin\awk -> C:\cygwin64\bin\gawk.exe Found: C:\cygwin64\bin\bash.exe Found: C:\cygwin64\bin\cat.exe Found: C:\Windows\system32\certutil.exe Not Found: clinfo Found: C:\Windows\system32\comp.exe Found: C:\Windows\system32\convert.exe Found: C:\cygwin64\bin\cp.exe Not Found: cpp (good!) Not Found: crontab Found: C:\cygwin64\bin\curl.exe Found: C:\Windows\system32\curl.exe Found: C:\cygwin64\bin\expand.exe Found: C:\Windows\system32\expand.exe Found: C:\cygwin64\bin\find.exe Found: C:\Windows\system32\find.exe Found: C:\Windows\system32\ftp.exe Not Found: gcc Found: C:\cygwin64\bin\gdb.exe Found: C:\cygwin64\bin\grep.exe Found: C:\cygwin64\bin\hostname.exe Found: C:\Windows\system32\hostname.exe Found: C:\cygwin64\bin\kill.exe Found: C:\Windows\system32\klist.exe Found: C:\cygwin64\bin\ld.exe Found: C:\cygwin64\bin\ls.exe Not Found: make Found: C:\cygwin64\bin\mv.exe Found: C:\Windows\system32\nslookup.exe Not Found: patch Found: C:\cygwin64\bin\perl.exe Found: C:\Windows\system32\replace.exe Found: C:\cygwin64\bin\rm.exe Found: C:\cygwin64\bin\sed.exe Found: C:\cygwin64\bin\sh.exe Found: C:\Windows\system32\shutdown.exe Found: C:\cygwin64\bin\sort.exe Found: C:\Windows\system32\sort.exe Found: C:\cygwin64\bin\ssh.exe Found: C:\cygwin64\bin\tar.exe Found: C:\Windows\system32\tar.exe Found: C:\cygwin64\bin\test.exe Found: C:\cygwin64\bin\timeout.exe Found: C:\Windows\system32\timeout.exe Found: C:\cygwin64\bin\vi.exe Found: C:\cygwin64\bin\vim.exe Found: C:\cygwin64\bin\whoami.exe Found: C:\Windows\system32\whoami.exe 92k 2015/02/12 C:\cygwin64\bin\cygaa-1.dll 53k 2013/11/01 C:\cygwin64\bin\cyganthy-0.dll 249k 2013/11/01 C:\cygwin64\bin\cyganthydic-0.dll 14k 2017/03/13 C:\cygwin64\bin\cyganthygobject-1.0-5.dll 51k 2013/11
