From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Westcoast Human <completely.and.totally.trash@gmail.com>
Subject: Re: [ANNOUNCEMENT] Updated: cygutils 1.4.16-7
Date: Mon, 27 Sep 2021 20:07:20 +0900 [thread overview]
Message-ID: <20210927200720.67275a3830a20bd5e44b3602@nifty.ne.jp> (raw)
In-Reply-To: <20210927191018.a56d0e99f3c4e212427db081@nifty.ne.jp>
On Mon, 27 Sep 2021 19:10:18 +0900
Takashi Yano wrote:
> On Sun, 26 Sep 2021 17:46:16 -0700
> Westcoast Human wrote:
> > I'm just going to jump in here and report what I think is an issue I
> > am having with 'putclip.'
> >
> > For years I've been using a Windows shortcut to execute a simple
> > filter function. It has recently stopped working. This is the 'target'
> > entry for the shortcut:
> > C:\Windows\System32\cmd.exe /c "c:\cygwin64\bin\getclip.exe |
> > c:\cygwin64\bin\tr.exe -s '\012\015' ' ' |
> > c:\cygwin64\bin\putclip.exe"
> >
> > This now wedges and is not interruptible with Ctrl-C, but closing the
> > CMD window kills everything. Task Manager shows that putclip is
> > apparently stuck in a loop waiting for something to happen as the
> > counts in "I/O Other" and "I/O Other bytes" keep increasing at a
> > regular rate (should a timeout error be incorporated, perhaps?)
>
> Could you please try
> cygwin 3.3.0-0.2.6c1f49f83fde (TEST)
> https://cygwin.com/pipermail/cygwin/2021-September/249475.html
> ?
This problem seems to be a problem of cygwin 3.2.0 which was
already fixed in git head by:
commit b4fc81edcc25b5c313ab3805dc0bcd015c370e62
Author: Takashi Yano <takashi.yano@nifty.ne.jp>
Date: Mon Apr 19 19:30:45 2021 +0900
Cygwin: console: Fix race issue regarding cons_master_thread().
- With this patch, the race issue regarding starting/stopping
cons_master_thread() introduced by commit ff4440fc is fixed.
Addresses:
https://cygwin.com/pipermail/cygwin/2021-April/248292.html
Thanks.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2021-09-27 11:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 6:37 Mark Geisert
2021-09-25 4:31 ` Takashi Yano
2021-09-25 7:23 ` Takashi Yano
2021-09-25 8:12 ` Takashi Yano
2021-09-26 9:44 ` Mark Geisert
2021-09-26 9:43 ` Mark Geisert
2021-09-26 9:40 ` Mark Geisert
2021-09-26 18:41 ` Doug Henderson
2021-09-27 0:46 ` Westcoast Human
2021-09-27 6:13 ` Brian Inglis
2021-09-27 6:29 ` Brian Inglis
2021-09-27 20:00 ` Richard Beels
2021-09-27 20:00 ` Richard Beels
2021-09-27 20:00 ` Richard Beels
2021-09-27 10:10 ` Takashi Yano
2021-09-27 11:07 ` Takashi Yano [this message]
2021-09-28 3:58 ` Westcoast Human
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=20210927200720.67275a3830a20bd5e44b3602@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=completely.and.totally.trash@gmail.com \
--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).