Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Denis PILAT <denis.pilat@st.com>
Cc: gdb-patches@sourceware.org
Subject: Re: '\r' only end-of-line
Date: Wed, 11 Oct 2006 17:36:00 -0000	[thread overview]
Message-ID: <u7iz6kb5h.fsf@gnu.org> (raw)
In-Reply-To: <452CC287.4050401@st.com> (message from Denis PILAT on Wed, 11 	Oct 2006 12:08:07 +0200)

> Date: Wed, 11 Oct 2006 12:08:07 +0200
> From: Denis PILAT <denis.pilat@st.com>
> Cc: gdb-patches@sourceware.org
> >
> >As for the \r case, don't such files fail in many more places?  It
> >looks like you need to test for \r in every place where we currently
> >test for \n, or am I missing something?
> >
> >
> Well, I thought reading your previous email on the other patch you just 
> accepted
> ( "What happens with a file that ends  in a sole `\r'?"),
> that MacOs files were supported by GDB. So I did some tests
> with such a file and found that there were a problem in the TUI that
> did not allow user to scroll these kind of source files. There are also
> problem in gdb command line. Both tell that the source file contains 
> only 1 line.
> 
> My patch just fixes this problem and allow scrolling of sources file in 
> the TUI, not more.
> 
> It does NOT aims at globally supporting MACOS files , as you said, there 
> should
> be plenty of failures elsewhere, and there are.
> I don't want to go into such a yard
> so let's forget about my patch if you think it's useless.

It's not useless to make GDB seamlessly work with all 3 types of
end-of-line formats, but that's a lot of work, so if you don't have
the resources to do that, it doesn't make sense to fix only this one
place, because, as you saw, it will fail in many others.


  parent reply	other threads:[~2006-10-11 17:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-09 15:25 [TUI] correctly display windows source files Denis PILAT
2006-10-09 18:01 ` Mark Kettenis
2006-10-09 19:28 ` Eli Zaretskii
2006-10-10 13:23   ` Denis PILAT
2006-10-10 15:08     ` '\r' only end-of-line Denis PILAT
2006-10-10 21:34       ` Eli Zaretskii
2006-10-11 10:08         ` Denis PILAT
2006-10-11 13:33           ` Daniel Jacobowitz
2006-10-11 13:57             ` Andrew STUBBS
2006-10-11 14:01               ` Daniel Jacobowitz
2006-10-11 14:44                 ` Andrew STUBBS
2006-10-11 15:05                   ` Daniel Jacobowitz
2006-10-11 17:47             ` Eli Zaretskii
2006-10-11 17:36           ` Eli Zaretskii [this message]
2006-10-16  8:51             ` Denis PILAT
2006-10-10 21:24     ` [TUI] correctly display windows source files Eli Zaretskii
2006-10-11  8:02       ` Denis PILAT
2006-10-11  8:39         ` Eli Zaretskii
2006-10-11 11:23           ` Frederic RISS

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=u7iz6kb5h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=denis.pilat@st.com \
    --cc=gdb-patches@sourceware.org \
    /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