public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: cygutils 1.4.16-4 (TEST)
Date: Fri, 20 Aug 2021 16:28:42 -0700	[thread overview]
Message-ID: <d94a9f67-efab-cc2a-1ee5-96353119d58e@maxrnd.com> (raw)
In-Reply-To: <20210820203518.97ced25c9a8b228b24b6fa0f@nifty.ne.jp>

Hi Takashi,

Takashi Yano via Cygwin wrote:
> On Tue, 17 Aug 2021 00:11:51 -0700
> Mark Geisert wrote:
>> The following test packages have been uploaded to the Cygwin distribution:
>>
>> * cygutils-1.4.16-4
>> * cygutils-extra-1.4.16-4
>> * cygutils-x11-1.4.16-4
>>
>> This release fixes a couple of issues reported in -3 and re-implements
>> getclip's capture of Unicode characters from the Windows clipboard using
>> a different method.  This was required because the original approach
>> would not work in 32-bit Cygwin operating on 64-bit Windows.
>>
>> IF YOU USE GETCLIP TO CAPTURE NON-ASCII CHARACTERS FROM THE WINDOWS
>> CLIPBOARD, PLEASE TEST THIS NEWEST GETCLIP TO MAKE SURE IT WORKS FOR YOU.
>> Report any issues to the main Cygwin mailing list.
[...]
>> In about two weeks time this package will be marked current unless bugs
>> are found during this test period.
[...]
> I tested the 1.4.16-4(TEST), and confirmed that cygstart, getclip
> and putclip can be executed on my old machine which does not have
> AVX instruction.

Thanks for testing!

> However, I encountered a problem with putclip.
> Run 'echo AAAAAAAA | putclip' and paste clipboard to notepad.exe.
> Pasted string is garbled in my environment.
> 
> What am I wrong with?

s/am I/are we/ :-\  I can reproduce this.  No idea what's wrong as there were no 
recent changes to putclip.  Let me dig further.  Is this something you've done 
routinely in the past and it was known to work?
Thanks for the report,

..mark

  reply	other threads:[~2021-08-20 23:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17  7:11 Mark Geisert
2021-08-20 11:35 ` Takashi Yano
2021-08-20 23:28   ` Mark Geisert [this message]
2021-08-21 15:06     ` Takashi Yano
2021-08-23 17:48       ` Christian Franke
2021-08-23 18:10         ` Corinna Vinschen
2021-08-23 20:58           ` Mark Geisert
2021-08-24  6:52             ` Mark Geisert
2021-08-24  7:40               ` Corinna Vinschen
2021-08-23 20:51         ` Mark Geisert

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=d94a9f67-efab-cc2a-1ee5-96353119d58e@maxrnd.com \
    --to=mark@maxrnd.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).