From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Unable to open the clipboard
Date: Sun, 9 Jan 2022 22:44:24 -0800 [thread overview]
Message-ID: <88da5384-72c5-7c45-b0d5-68703842f14c@maxrnd.com> (raw)
In-Reply-To: <ec70b02e-cf0e-c56f-db41-b678dacc04f5@maxrnd.com>
> Marco Atzeri wrote:
>> On 04.01.2022 19:08, Marco Atzeri wrote:
>>> On 04.01.2022 06:15, Mark Geisert wrote:
>>>> Mark Geisert wrote:
>>>>> I haven't been able to reproduce the issue with -7 or the more recent -8 test
>>>>> version. I suppose you might try -8 and see if it helps. Puzzling...
>>>>
>>>> Sorry, the {put,get}clip.exe are in cygutils-extra package. But -8 is correct.
>>>>
>>>> ..mark
>>>>
>>>
>>> Thanks Mark,
>>> -8 seems to work fine.
>>>
>>
>> Hi Mark,
>> just found another issue
>>
>> $ putclip < Announce_octave
>> Aborted (core dumped)
>>
>> It seems caused by the longest line (86 characters)
>>
>> $ cat Announce_octave | putclip
>> Aborted (core dumped)
>>
>> $ cat Announce_octave | sed -e "/html$/ d" | putclip
>>
>> of course the Clipboard is fine
>>
>> $ cat Announce_octave > /dev/clipboard
I'm unable to reproduce. If you happen to have a putclip.exe.stackdump left
behind, could you post that please?
..mark
next prev parent reply other threads:[~2022-01-10 6:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 14:34 Marco Atzeri
2022-01-03 15:59 ` Ken Brown
2022-01-03 17:47 ` Marco Atzeri
2022-01-04 0:25 ` Mark Geisert
2022-01-04 2:23 ` Marco Atzeri
2022-01-04 5:12 ` Mark Geisert
2022-01-04 5:15 ` Mark Geisert
2022-01-04 18:08 ` Marco Atzeri
2022-01-06 9:29 ` Marco Atzeri
2022-01-07 3:32 ` Mark Geisert
2022-01-10 6:44 ` Mark Geisert [this message]
2022-01-10 7:02 ` Marco Atzeri
2022-01-22 8:35 ` 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=88da5384-72c5-7c45-b0d5-68703842f14c@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).