Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Soren A Subject: Re: pasting clipboard always adds carriage return Date: Wed, 16 Oct 2002 04:00:59 +0000 (UTC) Organization: Occasionally Sporadically Lines: 25 Message-ID: References: <20021015035636 DOT 68599 DOT qmail AT web13708 DOT mail DOT yahoo DOT com> NNTP-Posting-Host: ny-kenton2a-572.buf.adelphia.net X-Trace: main.gmane.org 1034740859 16074 24.51.94.60 (16 Oct 2002 04:00:59 GMT) X-Complaints-To: usenet AT main DOT gmane DOT org NNTP-Posting-Date: Wed, 16 Oct 2002 04:00:59 +0000 (UTC) User-Agent: Xnews/L5 X-Archive: encrypt f m wrote around 14 Oct 2002 news:20021015035636 DOT 68599 DOT qmail AT web13708 DOT mail DOT yahoo DOT com: > I'm using cygwin-1.3.12-4 on WinME. I find that when I cut something > from the cygwin window, it always has a carriage return at the end > regardless of what application I paste it into. This only happens for > text copied to the clipboard from a cygwin window. I have checked > "Quick Edit" and unchecked "Fast Pasting". I can't find anything > about this in the FAQ, cygwin mailing list archive, or google. Is > there a way to prevent this? I always see this also, on Win9x. WinME is descended from Win9x. That is, IMHO, the nature of the problem: it is an artifact relating to the Windows console in these M$ OSs. It isn't a "Cygwin problem" I think. I've just learned to live with it. It isn't fixable by anything you can check or uncheck in Windoze. HTH, Soren A -- Just say NO to YAHAAPs! (http://groups.google.com/groups?&selm= Xns92991EB1F396ngrATT586ID%40204.127.36.1) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/