From: "Eli Zaretskii" <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: tromey@redhat.com, drow@false.org, otto.wyss@orpatec.ch,
gdb@sources.redhat.com
Subject: Re: GDB doesn't show the correct line
Date: Mon, 15 Nov 2004 16:06:00 -0000 [thread overview]
Message-ID: <01c4cacd$Blat.v2.2.2$9f8338a0@zahav.net.il> (raw)
In-Reply-To: <je6548dny4.fsf@sykes.suse.de> (message from Andreas Schwab on Mon, 15 Nov 2004 00:13:07 +0100)
> Cc: tromey@redhat.com, drow@false.org, otto.wyss@orpatec.ch,
> gdb@sources.redhat.com
> From: Andreas Schwab <schwab@suse.de>
> Date: Mon, 15 Nov 2004 00:13:07 +0100
>
> Because they look like non-canonical line endings, but can be interpreted
> as two line endings when using a strict interpretation. The first one
> could be a Unix newline followed by a Mac newline, or a non-canonical DOS
> newline (should non-canonical DOS newlines be recognized?). The second
> one could be a Mac newline followed by a DOS newline, or a spurious CR
> followed by a DOS newline (should spurious CRs be ignored?).
If we support \r Mac-style newlines, then (see Felix's message in this
thread), we cannot support non-canonical line-endings and we cannot
ignore spurious CRs.
next prev parent reply other threads:[~2004-11-15 4:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 19:24 Otto Wyss
2004-06-20 20:29 ` Daniel Jacobowitz
2004-06-21 17:56 ` Otto Wyss
2004-06-21 17:59 ` Daniel Jacobowitz
2004-06-21 18:15 ` Otto Wyss
2004-06-21 19:41 ` Daniel Jacobowitz
2004-11-13 20:50 ` Daniel Jacobowitz
2004-11-13 20:55 ` Otto Wyss
2004-11-13 21:43 ` Daniel Jacobowitz
2004-11-14 4:36 ` Otto Wyss
2004-11-13 21:46 ` Eli Zaretskii
2004-11-13 21:59 ` Daniel Jacobowitz
2004-11-14 5:30 ` Eli Zaretskii
2004-11-14 14:38 ` Tom Tromey
2004-11-14 21:43 ` Eli Zaretskii
2004-11-14 22:29 ` Andreas Schwab
2004-11-14 22:39 ` Eli Zaretskii
2004-11-15 4:41 ` Andreas Schwab
2004-11-15 16:06 ` Eli Zaretskii [this message]
2004-11-14 23:37 ` Felix Lee
2004-11-15 4:45 ` Eli Zaretskii
2004-06-23 11:54 ` Tarjei Knapstad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01c4cacd$Blat.v2.2.2$9f8338a0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=otto.wyss@orpatec.ch \
--cc=schwab@suse.de \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox