Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: dj@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Make cygwin use .gdbinit
Date: Mon, 12 Nov 2001 13:13:00 -0000	[thread overview]
Message-ID: <20011126183228.GA4788@redhat.com> (raw)
Message-ID: <20011112131300.OfUdcpUrY2N73prHx2w-XXcuQk_vh3HW3vSYADlw74Y@z> (raw)
In-Reply-To: <200111260755.JAA10760@is.elta.co.il>

On Mon, Nov 26, 2001 at 09:55:17AM +0200, Eli Zaretskii wrote:
>> Date: Sun, 25 Nov 2001 23:04:26 -0500
>> From: DJ Delorie <dj@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.
>
>My suggestion is similar:
>
>  When you start @value{GDBN}, it automatically executes commands from its
>  @dfn{init files}, normally called @file{.gdbinit}@footnote{The DJGPP
>  port of @value{GDBN} uses the name @file{gdb.ini} instead, due to the
>  limitations of file names imposed by DOS filesystems.}.
>
>This banishes the difference into a footnote, where it is less
>prominent, and also avoids the pitfall of saying that gdb.ini is only
>used on DOS.

That looks right to me.  How about the other section of the patch, though:

 @cindex @code{--nx}
 @cindex @code{-n}
 Do not execute commands found in any initialization files (normally
-called @file{.gdbinit}, or @file{gdb.ini} on PCs).  Normally,
+called @file{.gdbinit} or @file{gdb.ini} under MS-DOS).  Normally,
 @value{GDBN} executes the commands in these files after all the command
 options and arguments have been processed.  @xref{Command Files,,Command
 files}.

How about just removing the parenthetical expression entirely?  It was
never right to begin with.  What's a "PC"?  Isn't my linux system running
on a PC?

Since the next sentence references the section which discusses initialization
files can we just delete this entirely?

cgf


  parent reply	other threads:[~2001-11-26 18:32 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
2001-11-11 10:33           ` Eli Zaretskii
2001-11-25 23:55             ` Eli Zaretskii
2001-11-26 10:32             ` Christopher Faylor [this message]
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=20011126183228.GA4788@redhat.com \
    --to=cgf@redhat.com \
    --cc=dj@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