From: DJ Delorie <dj@redhat.com>
To: cgf@redhat.com
Cc: eliz@is.elta.co.il, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Make cygwin use .gdbinit
Date: Sun, 11 Nov 2001 09:57:00 -0000 [thread overview]
Message-ID: <200111260404.fAQ44Qx12366@greed.delorie.com> (raw)
In-Reply-To: <20011125193544.GA2355@redhat.com> (message from Christopher Faylor on Sun, 25 Nov 2001 14:35:44 -0500)
I suggest something like:
These files are normally named @file{.gdbinit} although filesystem
limitations require that they be named @file{gdb.ini} on some
platforms, such as DJGPP.
Although DJGPP also could look for .gdbinit first, then gdb.ini. It
will work on LFN-enabled systems. But the complaint about gdb.ini
would have to be silenced for DJGPP.
Also, there's no reason not to look for first .gdbinit and then
gdb.ini on *all* platforms, and warn the user only if *both* are
found.
PS: While DJGPP is indeed dos-based, most people don't realize it uses
the DOS simulator within Windows. So a technically true statement can
still be misleading. In the long war against MS trying to kill DOS,
we run into this kind of problem all the time.
WARNING: multiple messages have this Message-ID
From: DJ Delorie <dj@redhat.com>
To: cgf@redhat.com
Cc: eliz@is.elta.co.il, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Make cygwin use .gdbinit
Date: Sun, 25 Nov 2001 20:09:00 -0000 [thread overview]
Message-ID: <200111260404.fAQ44Qx12366@greed.delorie.com> (raw)
Message-ID: <20011125200900.wPclcCRkTTPnnMfgd-d4WebbHz6APqp0r1N22qWmh9M@z> (raw)
In-Reply-To: <20011125193544.GA2355@redhat.com>
I suggest something like:
These files are normally named @file{.gdbinit} although filesystem
limitations require that they be named @file{gdb.ini} on some
platforms, such as DJGPP.
Although DJGPP also could look for .gdbinit first, then gdb.ini. It
will work on LFN-enabled systems. But the complaint about gdb.ini
would have to be silenced for DJGPP.
Also, there's no reason not to look for first .gdbinit and then
gdb.ini on *all* platforms, and warn the user only if *both* are
found.
PS: While DJGPP is indeed dos-based, most people don't realize it uses
the DOS simulator within Windows. So a technically true statement can
still be misleading. In the long war against MS trying to kill DOS,
we run into this kind of problem all the time.
next prev parent reply other threads:[~2001-11-26 4:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 12:38 Christopher Faylor
2001-11-10 13:37 ` Eli Zaretskii
2001-11-10 21:53 ` Christopher Faylor
2001-11-25 11:14 ` Eli Zaretskii
2001-11-11 1:14 ` Eli Zaretskii
2001-11-11 8:09 ` Christopher Faylor
2001-11-11 9:57 ` DJ Delorie [this message]
2001-11-11 10:33 ` Eli Zaretskii
2001-11-25 23:55 ` Eli Zaretskii
2001-11-26 10:32 ` Christopher Faylor
2001-11-12 13:13 ` Christopher Faylor
2001-11-12 14:43 ` Eli Zaretskii
2001-11-12 21:19 ` Christopher Faylor
2001-11-26 12:34 ` Christopher Faylor
2001-11-26 11:23 ` Eli Zaretskii
2001-11-26 10:42 ` DJ Delorie
2001-11-12 13:22 ` DJ Delorie
2001-11-25 20:09 ` DJ Delorie
2001-11-25 11:35 ` Christopher Faylor
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=200111260404.fAQ44Qx12366@greed.delorie.com \
--to=dj@redhat.com \
--cc=cgf@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@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