From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33191 invoked by alias); 21 Feb 2019 16:12:13 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 33155 invoked by uid 89); 21 Feb 2019 16:12:12 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-spam-relays-external:ESMTPA X-HELO: resqmta-ch2-12v.sys.comcast.net Received: from resqmta-ch2-12v.sys.comcast.net (HELO resqmta-ch2-12v.sys.comcast.net) (69.252.207.44) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 21 Feb 2019 16:12:11 +0000 Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id woKJgkXqrpFrSwqxEgsIUo; Thu, 21 Feb 2019 16:12:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1550765528; bh=HtxCguO08kKCvrrl9hWG6XA9Z0Ct1mF1psH5z57EWbo=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=jT1skrBuppRkvMvbzOd06cMk5U7fNJRFtfj/b/Lpo58rqZi+YM1n2bw/4DR5dxmRc /eqoc9TDpjmDQs8ZjYr6gsNPAdOqeXZCkJ7WSk/cR426UtdPN2ZeQTb92dRWkSCToi WtbCa0H2EaH/srlpft6Qm1SYAHtMTeB2Ayrtockc9J7i6JddWBrewVbghDjZhf3CL9 sLM9rvP2S4rlSqxY41j0MMo4j90sIy6tTxeUGNuvNCNDK+44MQ8dshtgy2ApEXpT7Z 38UOF3VzeLAgYwnEqMDS/vxxlmWMcQ8m1RrKXuP1cNBxH6MbmtbJtazdpgEAgJ8ZdO lv7E7DRz9eWAg== Received: from pkoning.akdesign.com ([73.60.223.101]) by resomta-ch2-10v.sys.comcast.net with ESMTPA id wqwMgIqwWCZUAwqxDgGTgt; Thu, 21 Feb 2019 16:12:07 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedutddrtdekgdekjecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpefrrghulhcumfhonhhinhhguceophgruhhlkhhonhhinhhgsegtohhmtggrshhtrdhnvghtqeenucfkphepjeefrdeitddrvddvfedruddtudenucfrrghrrghmpehhvghlohepphhkohhnihhnghdrrghkuggvshhighhnrdgtohhmpdhinhgvthepjeefrdeitddrvddvfedruddtuddpmhgrihhlfhhrohhmpehprghulhhkohhnihhnghestghomhgtrghsthdrnhgvthdprhgtphhtthhopehtrhhomhgvhiesrggurggtohhrvgdrtghomhdprhgtphhtthhopegvlhhiiiesghhnuhdrohhrghdprhgtphhtthhopehguggsqdhprghttghhvghssehsohhurhgtvgifrghrvgdrohhrghenucevlhhushhtvghrufhiiigvpedt X-Xfinity-VMeta: sc=-100;st=legit Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: [PATCH] Handle \r\n in gdbreplay From: Paul Koning In-Reply-To: <87y369jfby.fsf@tromey.com> Date: Thu, 21 Feb 2019 16:12:00 -0000 Cc: Eli Zaretskii , gdb-patches@sourceware.org Content-Transfer-Encoding: quoted-printable Message-Id: <0A17F2B3-6BB5-4E7E-8E77-C9519C9EFA94@comcast.net> References: <20190221140513.29508-1-tromey@adacore.com> <83sgwhfa1o.fsf@gnu.org> <87y369jfby.fsf@tromey.com> To: Tom Tromey X-SW-Source: 2019-02/txt/msg00352.txt.bz2 > On Feb 21, 2019, at 11:06 AM, Tom Tromey wrote: >=20 >>>>>> "Eli" =3D=3D Eli Zaretskii writes: >=20 > Eli> I'm okay with treating \r\n as a single \n, but do we really want to > Eli> treat a single \r as if it were \n? I thought systems which used th= at > Eli> EOL convention are not really widespread, to say the least. >=20 > I normally handle \r this way out of habit I suppose. It doesn't matter > that much to me, I guess \r isn't likely to be seen or made by accident. Supposedly \r alone is newline in Mac OS 9 and before, which at this point = is sufficiently ancient history it may no longer be interesting. paul