From: Bob Rossi <bob_rossi@cox.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: text file formats
Date: Thu, 06 Apr 2006 19:32:00 -0000 [thread overview]
Message-ID: <20060406190742.GA2769@brasko.net> (raw)
In-Reply-To: <uek0a7ckx.fsf@gnu.org>
On Thu, Apr 06, 2006 at 10:01:34PM +0300, Eli Zaretskii wrote:
> > Date: Thu, 6 Apr 2006 10:05:42 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > Why are you going to tremendous lengths to accomodate non-native
> > newline conventions? Is there some good reason I've missed?
>
> I don't know if that's Bob's reason, but one good reason is that
> nowadays you can never know where (on what machine) the source files
> live, and who edits them on what platform. For example, some
> developers are so used to Microsoft's Visual Studio that they use it
> to edit sources to be compiled on Unix (via the network).
>
> So it does make sense to support non-native formats, although adding
> that to GDB would be a non-trivial job.
This is exactly my reasoning. Usually I agree 100% with Daniel, but in
this circumstance, I just think it's wrong to say "sorry, your out of
luck" to the user.
Bob Rossi
next prev parent reply other threads:[~2006-04-06 19:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 22:31 Bob Rossi
2006-04-05 23:39 ` Daniel Jacobowitz
2006-04-06 0:14 ` Bob Rossi
2006-04-06 1:17 ` Daniel Jacobowitz
2006-04-06 3:27 ` Bob Rossi
2006-04-06 3:35 ` Eli Zaretskii
2006-04-06 5:06 ` Daniel Jacobowitz
2006-04-06 13:03 ` Daniel Jacobowitz
2006-04-06 14:01 ` Bob Rossi
2006-04-06 14:41 ` Daniel Jacobowitz
2006-04-06 19:20 ` Eli Zaretskii
2006-04-06 19:32 ` Bob Rossi [this message]
2006-04-06 23:55 ` Daniel Jacobowitz
2006-04-07 13:33 ` Eli Zaretskii
2006-04-06 20:55 ` Paul Koning
2006-04-07 11:54 ` Eli Zaretskii
2006-04-06 19:07 ` Eli Zaretskii
2006-04-06 3:47 ` Eli Zaretskii
2006-04-06 4:29 ` Daniel Jacobowitz
2006-04-06 4:30 ` Daniel Jacobowitz
2006-04-06 3:43 ` Eli Zaretskii
2006-04-06 13:35 ` Bob Rossi
2006-04-06 19:01 ` Eli Zaretskii
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=20060406190742.GA2769@brasko.net \
--to=bob_rossi@cox.net \
--cc=eliz@gnu.org \
--cc=gdb@sources.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