From: "Nellis, Kenneth" <Kenneth.Nellis@xerox.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Cygwin clipboard flaky on Windows 7
Date: Fri, 17 Oct 2014 15:06:00 -0000 [thread overview]
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A702E83568F@USA7109MB022.na.xerox.net> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A702E835603@USA7109MB022.na.xerox.net>
From: Nellis, Kenneth
> This is interesting because just yesterday I was extensively copying and
> pasting from a pair of Notepad windows into my Mintty/bash session using
> getclip, and occasionally it would just paste in a single garbage
> character. So, this is different from the OP in that X is not involved.
>
> After seeing this post, I tried for nearly a half hour trying to discern a
> repeatable pattern to exhibit this behavior, but failed.
> Don't want to inject red herrings here, but I've only noticed this with
> two Notepad windows open and copying alternately from either.
> Also, it seems that selecting new notepad text, but neglecting to
> Ctrl+C may be somehow involved. Again, I've tried many combinations of
> this and have not been able to discern any pattern of when failure occurs.
>
> This one non-repeatable failure may be illustrative. Consider two Notepad
> windows open, A and B, and a mintty/bash shell window open.
> The following steps produced failure:
>
> Select text from A, Ctrl-C, getclip (worked), select text from B, Ctrl-C,
> getclip (worked), click somewhere in A to deselect text, click somewhere
> in B to deselect text, getclip (failed!).
I have a new theory on this, which may as well apply to the OP as well: PEBCAK.
After selecting text in Notepad and Ctrl-C copying, then clicking in the
mintty window to refocus the keyboard to run getclip, perhaps slopping clicking
caused Mintty's auto-copy-on-select feature to maybe capture an accidental
single-character selection, thus wiping out what was copied from Notepad.
I'll be more careful about clicking and post again if I can rule that out.
--Ken Nellis
next prev parent reply other threads:[~2014-10-17 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 11:28 Chris Stenton
2014-10-17 14:07 ` Nellis, Kenneth
2014-10-17 15:06 ` Nellis, Kenneth [this message]
2014-10-17 17:15 ` Doug Henderson
2014-10-21 12:15 ` Jon TURNEY
2014-10-21 14:26 ` Chris Stenton
2014-10-31 14:44 ` Chris Stenton
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=0D835E9B9CD07F40A48423F80D3B5A702E83568F@USA7109MB022.na.xerox.net \
--to=kenneth.nellis@xerox.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).