Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: "Antoine Levy-Lambert" <antoine AT antbuild DOT com>
Subject: Re: cut and paste problem with xemacs Was Re: [ANNOUNCEMENT] Available   for test: cygwin-1.5.0-1
Date: Fri, 25 Jul 2003 21:02:29 +0200
Lines: 29
Message-ID: <bfrunc$kjh$1@main.gmane.org>
References: <20030710041843 DOT C29AA6C594 AT redhat DOT com><bfhc7h$v12$1 AT main DOT gmane DOT org> <16156 DOT 22413 DOT 865281 DOT 664360 AT phish DOT entomo DOT com> <008401c34fcf$7d9cd2c0$020200c0 AT DJ0X820J> <3F1C6B26 DOT B4EA0216 AT acm DOT org> <bfp25g$c5$1 AT main DOT gmane DOT org> <3F2011BD DOT E699303 AT acm DOT org>
X-Complaints-To: usenet AT main DOT gmane DOT org
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

David Rothenberger wrote :
>Any suggestions would be appreciated, even if its just "try looking at
>somefile.c".  I don't mind investigation and can go with limited info;
>I'm just out of ideas now.
One idea would be to look at the source code of xemacs.
I presume that the copy and paste functions of xemacs (key combinations
Esc-W and C-y) are lisp functions which call directly or indirectly C API
functions.
Looking at these function calls would begin to shed light on the problem.

The other question on the cygwin side : what is the official or recommended
way of accessing the cut and paste buffer for an application written in C
(xemacs) and running under Windows+cygwin.

When we will have answers to both these questions, we can determine whether
:
- xemacs was using an undocumented feature of cygwin to interact with the
Windows cut and paste buffer, or whether the official cygwin API has
changed,
- other option : to the contrary, xemacs is programmed properly and there
has been a mistake in the code changes done in cygwin between 1.3.x and 1.5

I would be delighted to help, but I am busy at the moment, so I do not make
any promise.

Cheers,
Antoine




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/