From: Westcoast Human <completely.and.totally.trash@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: cygutils 1.4.16-7
Date: Sun, 26 Sep 2021 17:46:16 -0700 [thread overview]
Message-ID: <CAKwdsS8S867CcGtO6wSnP8_bPJNYgZZyR6YjFWbrrcNzSySvHQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ1FpuPuqtpkOpeKSqsG7MUqh+GKK4=Qv57=8TYSRJ2tk9v6dQ@mail.gmail.com>
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?)
I can use Task Manager to generate a Windows dump file, if that helps.
I have extensive embedded systems programming experience, but know
next to nothing about the internals of Windows or Cygwin.
Windows 10.
next prev parent reply other threads:[~2021-09-27 0:46 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 [this message]
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
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=CAKwdsS8S867CcGtO6wSnP8_bPJNYgZZyR6YjFWbrrcNzSySvHQ@mail.gmail.com \
--to=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).