Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com content-class: urn:content-classes:message Subject: unix/dos text question MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Fri, 23 Mar 2001 11:18:21 +1100 Message-ID: Thread-Topic: unix/dos text question Thread-Index: AcCzLsSJiS+pGaFLQ/awZr2+g3u9Ow== From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id TAA13402 /dev/clipboard is a block/stream device... but it's pretty much guaranteed that there will be dos/unix mode issues: unix mode cygwin - the text when copied to (say) notepad will still be unix text. Likewise text copied from notepad to cygwin may have extra characters. dos mode cygwin - shouldn't have any surprises. Does the filehandler take care of that for me, or does the clipboard device need to be aware in some fashion? Ideally the clipboard gets the file data already translated :] The catch is that when writing the CF_TEXT format for windows applications to get from cygwin it should _always_ be dos mode IMO. (Cygwin apps will get the native format, which should be in whatever file mode the user is using). Pointers to routines are hereby solicted :] Rob