From: Denis Excoffier <cygwin@Denis-Excoffier.org>
To: cygwin@cygwin.com
Cc: Denis Excoffier <cygwin@Denis-Excoffier.org>,
Mark Geisert <mark@maxrnd.com>
Subject: Re: [ANNOUNCEMENT] Updated: cygutils 1.4.16-8 (Test)
Date: Sun, 14 Nov 2021 18:23:47 +0100 [thread overview]
Message-ID: <95DF7281-9391-4AEE-9427-7351DA47DBDE@Denis-Excoffier.org> (raw)
In-Reply-To: <announce.20211103095939.14663-1-mark@maxrnd.com>
Hello,
> On 2021-11-03 10:59, Mark Geisert wrote:
>
> The following packages have been uploaded to the Cygwin distribution:
>
> * cygutils-1.4.16-8
> * cygutils-extra-1.4.16-8
> * cygutils-x11-1.4.16-8
The '-u' or '-d' option of getclip does not seem to work properly under xterm.
How to reproduce:
1) Open an xterm
2) Select a simple piece of text (with no line ending)
3) getclip -u
4) Observe 'Segmentation fault(core dumped)'
If step 2 is replaced by ‘printf AAAA | putclip', no error.
If step 3 is replaced by ‘getclip’, no error.
I can’t tell whether this is new or not.
Remarks:
1) If (under xterm) i select a piece of text with a line end, then i can observe ‘\r\n’ at the end (using getclip | od -c)
2) If i select a piece of text with a line end with putclip, i can only observe ‘\n’ at the end (echo "AAAA" | putclip | getclip | od -c)
3) I launch ‘xwin’ with ‘option -clipboard’ (the default), i suppose this does not matter
4) It might be related to xorg-server-21.1.0-1 (TEST) that i installed recently (2021-11-04), however xwinclip-21-1.0-1 didn’t come with the rest
Regards,
Denis Excoffier.
next prev parent reply other threads:[~2021-11-14 17:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 9:59 Mark Geisert
2021-11-03 13:04 ` Takashi Yano
2021-11-04 4:31 ` Mark Geisert
2021-11-04 4:58 ` Thomas Wolff
2021-11-04 8:47 ` Mark Geisert
2021-11-04 20:08 ` Brian Inglis
2021-11-05 3:20 ` Takashi Yano
2021-11-05 5:40 ` Mark Geisert
2021-11-05 8:06 ` Takashi Yano
2021-11-05 8:53 ` Mark Geisert
2021-11-14 17:23 ` Denis Excoffier [this message]
2021-11-14 17:55 ` Mark Geisert
2021-11-14 17:55 ` Brian Inglis
2021-11-21 10:36 ` Mark Geisert
2021-11-21 14:51 ` Jon Turney
2021-11-22 7:08 ` Andrey Repin
2021-11-22 8:14 ` Takashi Yano
2021-11-23 9:08 ` 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=95DF7281-9391-4AEE-9427-7351DA47DBDE@Denis-Excoffier.org \
--to=cygwin@denis-excoffier.org \
--cc=cygwin@cygwin.com \
--cc=mark@maxrnd.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).