From: Mark Geisert <mark@maxrnd.com>
To: cygwin-announce@cygwin.com
Cc: Mark Geisert <mark@maxrnd.com>
Subject: Updated: cygutils 1.4.16-6
Date: Mon, 30 Aug 2021 01:57:46 -0700 [thread overview]
Message-ID: <20210830014157.30498-1-> (raw)
The following packages have been uploaded to the Cygwin distribution:
* cygutils-1.4.16-6
* cygutils-extra-1.4.16-6
* cygutils-x11-1.4.16-6
This update fixes two putclip issues reported by Takashi Yano:
1) Varying amounts of garbage after a putclip of non-ASCII chars, and
2) Occasional "Couldn't write CF_TEXT format to the clipboard" errors.
The first was caused by unterminated input strings; the second by
OpenClipboard() failing due to another process holding the clipboard.
There is now a specific diagnostic for that situation.
I'm aware of one more issue with putclip. Intermittently, using putclip
to place non-ASCII characters on the clipboard instead places a number
of "?" characters. If you de-select, re-select, and then repeat the
putclip command, the non-ASCII chars are placed as they should be. This
occurs whether your "paste" operation is from the application menu (e.g.
Edit->Paste) or via the mouse. I've tried a couple remedies but have
not yet found a solution.
Happy Monday,
..mark
--
"Always make new mistakes."
reply other threads:[~2021-08-30 8:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210830014157.30498-1- \
--to=mark@maxrnd.com \
--cc=cygwin-announce@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).