public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: cts.private@yahoo.com
Subject: Re: fvwm ignores clickToFocus for function keys
Date: Mon, 27 Sep 2010 15:26:00 -0000 [thread overview]
Message-ID: <4CA0B7BE.5060701@dronecode.org.uk> (raw)
In-Reply-To: <297050.63399.qm@web63705.mail.re1.yahoo.com>
On 26/09/2010 12:28, Charles Smith wrote:
> This conversation was transferred from the cygwin main list because Larry Hall said it was xfree-specific...
>
> From: Morgan Gangwere<0 dot fractalus at gmail dot com>
>> Sounds like something is trashing a buffer... however I'm not entirely
>> sure.
> ...
>> Sounds oddly configuration related... then again, i don't use fvwm on
>> windows.
>
> My suspicion is that it has to do with the cut-buffers/clip-board-mechanism, somehow.
>
> I'd said previously that what gets sent (when a function key is pressed but the mouse cursor isn't over the in-focus window) is the unmapped version of the function key. It might also be some earlier contents of the cut-buffer, or something like that. I'm still trying to track it down.
>
> Being able to cut-and-paste between windows and cygwin is important, and I'm glad that this evolving capability is so far along... but is it possible to disable it, at least for debugging purposes?
'man XWin' [1] documents the -noclipboard option.
[1] http://x.cygwin.com/docs/man1/XWin.1.html
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2010-09-27 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 11:28 Charles Smith
2010-09-27 15:26 ` Jon TURNEY [this message]
2010-10-26 20:04 Charles Smith
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=4CA0B7BE.5060701@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cts.private@yahoo.com \
--cc=cygwin-xfree@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).