From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin/X XWinrc menu no longer launches after recent updates
Date: Wed, 04 Mar 2020 19:05:00 -0000 [thread overview]
Message-ID: <5dd4f9c8-5e69-3355-6b80-6ab953475715@SystematicSw.ab.ca> (raw)
In-Reply-To: <f5by2shgkqv.fsf@ecclerig.inf.ed.ac.uk>
On 2020-03-03 15:02, Henry S. Thompson wrote:
> cygcheck output attached, just in case...
>
> Per previous message, had to interrupt id, which was hanging, which
> produced
>
> garbled output from "id" command - no uid= found
>
> while cygcheck carried on...
> and then hung with Process Explorer showing
>
> bash.exe
> bash.exe
> cygcheck.exe
> cmd.exe
> cygrunsrv.exe
As cygcheck is a Windows msvcrt.dll program, not a Cygwin cygwin1.dll program,
it uses Windows popen which runs commands under $COMSPEC rather than $SHELL, and
that can be affected by {HKLM,HKCU}/Software/Microsoft/Command Processor/
registry entries e.g.:
$ regtool list -v /proc/registry/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Command\
Processor/
DefaultColor (REG_DWORD) = 0x00000000 (0)
EnableExtensions (REG_DWORD) = 0x00000001 (1)
CompletionChar (REG_DWORD) = 0x00000040 (64)
PathCompletionChar (REG_DWORD) = 0x00000040 (64)
$ regtool list -v /proc/registry/HKEY_CURRENT_USER/SOFTWARE/Microsoft/Command\
Processor/
Autorun (REG_EXPAND_SZ) = "@chcp 65001 >nul"
CompletionChar (REG_DWORD) = 0x00000009 (9)
DefaultColor (REG_DWORD) = 0x00000000 (0)
EnableExtensions (REG_DWORD) = 0x00000001 (1)
PathCompletionChar (REG_DWORD) = 0x00000009 (9)
runs chcp 65001 at cmd startup, but could also do much more and different.
--
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
next prev parent reply other threads:[~2020-03-04 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 5:14 Roland Roberts
2020-03-03 9:53 ` Takashi Yano
2020-03-03 12:18 ` Henry S. Thompson
2020-03-03 12:35 ` Takashi Yano
2020-03-03 12:40 ` Henry S. Thompson
2020-03-03 12:59 ` Takashi Yano
2020-03-03 21:43 ` Henry S. Thompson
2020-03-03 22:20 ` Brian Inglis
2020-03-03 23:25 ` Brian Inglis
2020-03-04 1:12 ` Henry S. Thompson
2020-03-03 23:46 ` Henry S. Thompson
2020-03-04 19:05 ` Brian Inglis [this message]
2020-03-04 19:05 ` Henry S. Thompson
2020-03-04 8:59 ` Roland Roberts
2020-03-08 2:14 ` Roland Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5dd4f9c8-5e69-3355-6b80-6ab953475715@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).