Your message dated Sun, 4 Dec 2005 16:47:26 +0100
with message-id <[EMAIL PROTECTED]>
and subject line kate turns newlines into windows style 0D0A
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 11 Dec 2003 01:30:26 +0000
>From [EMAIL PROTECTED] Wed Dec 10 19:30:26 2003
Return-path: <[EMAIL PROTECTED]>
Received: from s2.ukfsn.org (mail.ukfsn.org) [217.158.120.143] 
        by master.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1AUF1X-0002QN-00; Wed, 10 Dec 2003 18:49:47 -0600
Received: from localhost (dsl213-218-232-133.as15444.net [213.218.232.133])
        by mail.ukfsn.org (Postfix) with SMTP id 82E0EE6A93
        for <[EMAIL PROTECTED]>; Thu, 11 Dec 2003 00:48:05 +0000 (GMT)
Received: (qmail 2420 invoked from network); 11 Dec 2003 00:55:54 -0000
Received: from unknown (HELO dragon) (127.0.0.1)
  by localhost with SMTP; 11 Dec 2003 00:55:54 -0000
Date: Thu, 11 Dec 2003 00:55:53 +0000
From: Andy Baxter <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: kate turns newlines into windows style 0D0A
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; Format=Flowed; DelSp=Yes; charset=ISO-8859-1
Content-Disposition: inline
X-Mailer: Balsa 2.0.15
Lines: 21
Content-Transfer-Encoding: quoted-printable
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 
        2.60-master.debian.org_2003_11_25-bugs.debian.org_2003_11_20 
        (1.212-2003-09-23-exp) on master.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no 
        version=2.60-master.debian.org_2003_11_25-bugs.debian.org_2003_11_20
X-Spam-Level: 

package: kate
version: 2.1

I'm getting an occasional error with kate, where it turns all the =20
newline characters into windows-style 0D0A pairs when I save a file. =20
This means the perl scripts I'm writing won't run. I have no idea why =20
this is happening, but I have checked it a few times with the hex =20
editor in midnight commander, and it is cured by doing:
 cat file | tr -d "\015" > newfile.

Once it's started happening with a particular file, it carries on =20
happening until I restart kate, but other files I have open at the same =20
time are not affected.

I like kate as an editor, so it would be nice if this was fixed, so I =20
know I can rely on it not screwing up my files.

If you want a copy of the particular file this has been happening with, =20
I can send it.

andy baxter.

---------------------------------------
Received: (at 223630-done) by bugs.debian.org; 4 Dec 2005 15:48:07 +0000
>From [EMAIL PROTECTED] Sun Dec 04 07:48:07 2005
Return-path: <[EMAIL PROTECTED]>
Received: from trichet.fr.eu.org ([82.233.187.16])
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1Eiw5u-0004k8-V4
        for [EMAIL PROTECTED]; Sun, 04 Dec 2005 07:48:07 -0800
Received: by trichet.fr.eu.org (Postfix, from userid 1000)
        id 562E3241FA; Sun,  4 Dec 2005 16:47:28 +0100 (CET)
From: Olivier Trichet <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: kate turns newlines into windows style 0D0A
Date: Sun, 4 Dec 2005 16:47:26 +0100
User-Agent: KMail/1.8.2
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[EMAIL PROTECTED]>
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-2.5 required=4.0 tests=BAYES_00,RCVD_IN_SORBS 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Hello,
without the relevant file, requested 2 years ago, this bug can be close.

bye,
Olivier


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to